Linked by Thom Holwerda on Mon 6th Aug 2012 21:50 UTC, submitted by iseyler
Thread beginning with comment 530166
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Please elaborate how it is untrue.
Quite simply the fact that asm isn't a must. We'll take the first item on your list as an example -- drivers. I invite you to join any of the numerous mailing lists used for Linux driver development. Ask people who actually write drivers if they agree that asm is a must and you will get a resounding no. For that matter, many of the guys writing drivers have zero asm experience. I have a friend who has worked for a handful of major chip makers and the only requirement placed on him, ever, was his willingness to sign NDA's. He also has no asm experience.
Since you made the claim, perhaps you should explain why you think it is, despite the fact we already know it isn't.





Member since:
2011-08-08
- drivers;
- operating systems utilities;
- games;
- compilers (either ahead-of-time or JIT based);
- audio or video codecs;
- develop applications that need to run in embedded systems
- numeric code for statistics like FFT
- optimization of code compreension
Than knowing Assembly is really a must.
While being well-versed in asm can have advantages, saying it's a must for at least half the things you've listed is absolutely untrue.