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’m guessing CF stands for cluster fuck.
Firefox, notepad ++, PuTTy
It isn’t always that they don’t know what they want, sometimes they just don’t know how to describe what they want, or they may know what they don’t want.
Ooooh, now plot the avg wage across this period. Y=min wage.
Video shows three new origins plus the ability to have non-gestalt consciousness. New megastructures.
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.
I see texting as a method of asynchronous communication. I tell people, “If you need a fast reply from me, call, don’t text.”
It could be they just wanted to checkin and see how you were, not really looking to have a conversation. I think it really depends on what the opening text was.
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.