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
Hmmm, it almost seems like poor leadership shouldn’t have spent 43 billion on stock buybacks over the last 10 years. Or, you know, resolve the strike and get your cash flow moving again.
Thank you both for a positive example of challenging someone’s post.
If those instruction sets take up a set place on the processing pipeline, eliminating them could be a huge performance boost. Additionally, the removal of the instruction sets would reduce the size of the chip’s die which could result in shorter signal paths.
I’m guessing CF stands for cluster fuck.
Firefox, notepad ++, PuTTy
Ooooh, now plot the avg wage across this period. Y=min wage.
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.
They didn’t ban third party apps. They increased the pricing for using the api to a rate higher than most third party apps could afford with their business models.
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.