I agree. I simply think, the assembly model will be replaced. There will eventually be a new, "better," set of principles. For reasoning about library gluing

I agree. I simply think, the assembly model will be replaced. There will eventually be a new, "better," set of principles. For reasoning about library gluing. > Knowledge of the underlying machine is irrelevant. > As you look back on your assembly experience later, you'll realize this is false. Better to clarify: truly deep knowledge of the underlying machine is irrelevant. At this point, I'd say I'm immensely richer from "thinking" about assembly. Nowhere else would I have truly learnt about CPU cycle times to copy data from register to register to call stack, and back. The concept of "time to copy data" is highly present in networking and other fields. Important to know that "C" and other high level languages abstract over it. I'm not entirely sure my knowledge of JTAG debugging/Rust borrow checker is ever going to be substantially useful. The time/benefit equation of doing all that work was... less than ideal. In hindsight, maybe an afternoon of assembly copying data from place to place, seems like "all" the big picture learning I needed? Then again. Maybe I invested far more time than undergraduate courses spend on the topic, regardless.