4 ms·
In the abstract, obviously any bit of knowledge is worth having. For assembly, I'd even bet the value you get from learning it outweighs the effort you put in.
by scarmig 15y ago
In the abstract, obviously any bit of knowledge is worth having. For assembly, I'd even bet the value you get from learning it outweighs the effort you put in.
The relevant question, though, is it at the margins the best use of your time?
Having a solid grasp of the Wikipedia-level knowledge of assembly is very valuable, but beyond that I'd be skeptical. Sure, you could learn it--but you could also learn about other topics, like writing a compiler, the theory of operating systems, understanding the layers of the TCP/IP stack, or working in a purely functional language like Haskell. All or any of those might be a better use of your time. So might learning to salsa, building social capital by hanging out with friends, or learning to bake bread.
So, maybe? But only if you're very curious about it (a good thing!) and have also knocked off other relatively more valuable and lower hanging fruit.
Of course, I've not taken the time to learn it, so it's quite likely there are some hidden benefits I've not managed to grok.
- sliverstorm 15y agoHow on earth can you write a compiler if you don't understand anything about assembly?
- scarmig 15y agoThe target language doesn't have to be assembly or machine code. Plus, that's just one of several steps, and not necessarily the most interesting.
- wglb 15y agoActually, the code generation part was the part that I found was the most interesting and challenging. The best part of the fun was generating sequences of instructions that the assembly-language guys wouldn't write becase they were too confusing.