jamesh wrote:I've been away, but an now refreshed and ready to argue.
Assembler. Worth learning the principles, because occasionally you need to dive down and see what happening at that level when debugging.
And that's it. It's of very little use in industry, and most decent compilers are within a % of producing code as good as hand assembler.
BUT, here at Broadcom, on the GPU used on the Raspi, we do use assembler occasionally, but out of necessity when moving from scaler to vector code - our compiler doesn't handle vector code at all, so all that stuff needs to be in assembly.
So what your saying is you DO need assembly coders, but for the bread and butter stuff, you can use those cheaper C programmers.
lots of decent C programmers around
No ones saying that theres 100,1000 of jobs for assembly programmers.
What we are saying, is if you want to be paid top $ as a programmer, you need to learn assembly, its supply and demand.
You said it yourself
so all that stuff needs to be in assembly
if a Co need something and theres not many programmers that can do decent assembly.
Those that can, can ask top $.
Also this very ? was asked on "adafruit ask an engineer" and she answer yes theres is a need, as Co want to save penny's on low spec chips, the only way to make them work is use assembly.
Add to that, that one of the main reason they changed from BIOS to UEFI
was a shortage of assembly programmers
http://www.edn.com/electronics-news/431 ... OS-to-UEFI
The silicon vendor "wish list" for the BIOS continued to grow. There was a desire to be able to use a high-level language such as C for driver development by standardizing on interfaces and coding practices, thereby easing driver development. The use of C would also help address a growing shortage of assembly language programmers.
Shortage, does not mean no jobs and are the assembly programmers higher paid ?.