Assembly requires a knowledge of the cpu architecture pipeline and memory storage addressing. Those concepts are generally abstracted away in modern languages
Assembly requires a knowledge of the cpu architecture pipeline and memory storage addressing. Those concepts are generally abstracted away in modern languages
I would prefer it to be opt in, instead of opt out. Maybe the centralized opt out won’t be as toothless as the do not call list.
Zipper merge is effective if it takes place at the end of the line, not the merge point. Essentially as traffic backs up, the merge point should back up as well. That isn’t practical in reality; you can’t dynamically move the merge point IRL.
I said modern programming languages. I do not consider C a modern language. The point still stands about abstraction in modern languages. You don’t need to understand memory allocation to code in modern languages, but the understanding will greatly benefit you.
I still contend that knowledge of the cpu pipeline is important or else your code will wind up with a bunch of code that is constantly resulting in CPU interrupts. I guess you could say you can code in assembly without knowledge of the cpu architecture, but you won’t be making any code that runs better the output code from other languages.