Hello,

More of my philosophy about pedagogy and about good education and more of my thoughts..

I am a white arab, and i think i am smart since i have also
invented many scalable algorithms and algorithms..

I think i am highly smart, and i have passed two certified IQ tests and i have scored above 115 IQ, so now i will talk more about pedagogy
and how to be efficient education, so i am for example knowing
how to learn really fast and efficiently the following programming languages: C++ and C# and Go and Rust and Raku(formerly known as Perl6), so i think that my pedagogical way of doing is working, since i think that my way of learning is also mostly about quality, not quantity, since my way of doing is that i have to smartly spot or detect the most efficient high level paths(not the inside as learning) as wich tutorials and wich books and wich chapters that permit me to learn efficiently and fast, and after that i am also smartly maximizing at best efficiency of learning and smartly maximizing at best simplicity of learning, so i think that it is a good way of doing since i am doing it and it is working.

And more of my philosophy about Raku, formerly known as Perl6..

Raku, formerly known as Perl6, is a very interesting,
very powerful programming language that represents the
next evolution of Perl.

In my opinion, it fixes many of the problems with Perl5.
the features of Raru on their own are pretty compelling.

It has most of the features you would expect in most
modern programming languages:

Classes, first-class functions, asynchronous programming,
and all the normal structured programming stuff—in addition
to the normal Perl stuff with regular expressions and string manipulation.

However, it also has a lot of features that are not found
in many other languages, and certainly not usually in the same
one.

Optional typing. Similar to TypeScript or Julia, types may be declared, but are not required. Unlike Python, declared types will be enforced.

Pattern matching. Like Haskell, different function definitions can be defined for different input values.

Multiple dispatch. Like Julia or Common Lisp, different function bodies can be defined for different sets of argument types (a bit like pattern matching, but on types instead of values).

Lazily-generated sequences, like Haskell or Clojure.

Lisp-like AST macros.

Junctions—a feature unique to Raku as far as I know, but similar to
sum types (a.k.a. algebraic data types or variant types). However,
Junction types are more than merely a sum, and may include logical expressions in their definitions.

Built in syntax for defining grammars and generating parsers.

Raku is a weird confluence of Perl-like features and extremely sophisticated abstractions to come out of programming language research.

Raku is a language that has it all.

It somehow fits. Where Perl has always been the poster-child for dealing with patterns and strings, Raku extends ideas about patterns into other aspects of the language; The type system, function dispatches, and even to the code of the program itself. It’s almost as if the entire language is some kind of engine for reasoning about patterns—both textual and symbolic.

Python uses a global interpreter lock, you can't execute two threads at the same time. Raku, formerly known as Perl6, can.

Raku, formerly known as Perl6, has a great chance of adoption for a variety of reasons. There are no popular dynamic languages with a working concurrency model (I'm looking at you, GIL); Perl 6 has a working concurrency model.. With Moore's law coming to an end,
this is a huge advantage. Further, it goes far beyond the primitive threads and locks which languages tend to offer.

I'd also point out that it has a very advanced OO model which pretty much leaves most competitors in the dust. On top of that, your classes have fewer lines of code and are easier to read.

I am also working with Raku, formerly known as Perl6, and i invite you
to download the following interesting book about Raku in a PDF format so that to learn it:

https://greenteapress.com/wp/think-perl-6/

And you can download the stable version of Raku, formerly known as Perl6, from the following website:

https://rakudo.org/

More of my thoughts about technology and about Apple Silicon M1 Emulating x86 and more of my thoughts..

I have just looked at the following articles about Rosetta 2 and the benchmarks of Apple Silicon M1 Emulating x86:

https://www.computerworld.com/article/3597949/everything-you-need-to-know-about-rosetta-2-on-apple-silicon-macs.html

and read also here:

https://www.macrumors.com/2020/11/15/m1-chip-emulating-x86-benchmark/

But i think that the problem with Apple Silicon M1 and the next Apple Silicon M2 is that Rosetta 2 only lets you run x86–64 macOS apps. That would be apps that were built for macOS (not Windows) and aren't 32-bit. The macOS restriction eliminates huge numbers of Windows apps, and 64-bit restriction eliminates even more.

Also read the following:

Apple says new M2 chip won’t beat Intel’s finest

Read more here:

https://www.pcworld.com/article/782139/apple-m2-chip-wont-beat-intels-finest.html

And here is what i am saying on my following thoughts about technology about Arm Vs. X86:

More of my philosophy about the Apple Silicon and about Arm Vs. X86 and more of my thoughts..

I invite you to read carefully the following interesting article so
that to understand more:

Overhyped Apple Silicon: Arm Vs. X86 Is Irrelevant

https://seekingalpha.com/article/4447703-overhyped-apple-silicon-arm-vs-x86-is-irrelevant

More of my philosophy about code compression of RISC-V and ARM and more of my thoughts..

I think i am highly smart, and i have just read the following paper
that says that RISC-V Compressed programs are 25% smaller than RISC-V programs, fetch 25% fewer instruction bits than RISC-V programs, and incur fewer instruction cache misses. Its code size is competitive with other compressed RISCs. RVC is expected to improve the performance and energy per operation of RISC-V.

Read more here to notice it:

https://people.eecs.berkeley.edu/~krste/papers/waterman-ms.pdf

So i think RVC has the same compression as ARM Thumb-2, so i think
that i was correct in my previous thoughts , read them below,
so i think we have now to look if the x86 or x64 are still more cache friendly even with Thumb-2 compression or RVC.

More of my philosophy of who will be the winner, x86 or x64 or ARM and more of my thoughts..

I think i am highly smart, and i think that since x86 or x64 has complex instructions and ARM has simple instructions, so i think that x86 or x64 is more cache friendly, but ARM has wanted to solve the problem by compressing the code by using Thumb-2 that compresses the code, so i think Thumb-2 compresses the size of the code by around 25%, so i think
we have to look if the x86 or x64 are still more cache friendly even with Thumb-2 compression, and i think that x86 or x64 will still optimize more the power or energy efficiency, so i think that there remains that since x86 or x64 has other big advantages, like the advantage that i am talking about below, so i think the x86 or x64 will be still successful big players in the future, so i think it will be the "tendency". So i think that x86 and x64 will be good for a long time to make money in business, and they will be good for business for USA that make the AMD or Intel CPUs.

More of my philosophy about x86 or x64 and ARM architectures and more of my thoughts..

I think i am highly smart, and i think that x86 or x64 architectures
has another big advantage over ARM architecture, and it is the following:

"The Bright Parts of x86

Backward Compatibility

Compatibility is a two-edged sword. One reason that ARM does better in low-power contexts is that its simpler decoder doesn't have to be compatible with large accumulations of legacy cruft. The downside is that ARM operating systems need to be modified for every new chip version.

In contrast, the latest 64-bit chips from AMD and Intel are still able to boot PC DOS, the 16-bit operating system that came with the original IBM PC. Other hardware in the system might not be supported, but the CPUs have retained backward compatibility with every version since 1978.

Many of the bad things about x86 are due to this backward compatibility, but it's worth remembering the benefit that we've had as a result: New PCs have always been able to run old software."

Read more here on the following web link so that to notice it:

https://www.informit.com/articles/article.aspx?p=1676714&seqNum=6

So i think that you can not compare x86 or x64 to ARM, since it is
not just a power efficiency comparison, like some are doing it by comparing
the Apple M1 Pro ARM CPU to x86 or x64 CPUs, it is why i think that x86 or x64 architectures will be here for a long time, so i think that they will be good for a long time to make money in business, and they are a good business for USA that make the AMD or Intel CPUs.

More of my philosophy about weak memory model and ARM and more of my thoughts..

I think ARM hardware memory model is not good, since it is a
weak memory model, so ARM has to provide us with a TSO memory
model that is compatible with x86 TSO memory model, and read what Kent Dickey is saying about it in my following writing:

ProValid, LLC was formed in 2003 to provide hardware design and verification consulting services.

Kent Dickey, founder and President, has had 20 years experience in hardware design and verification. Kent worked at Hewlett-Packard and Intel Corporation, leading teams in ASIC chip design and pre-silicon and post-silicon hardware verification. He architected bus interface chips for high-end servers at both companies. Kent has received more than 10 patents for innovative work in both design and verification.