I'm studying the architecture and implementation in MIPS, but since I'm not working at a low level, what I'm doing are basic exercises in any beginning of learning, I wonder what are the difficulties and real problems of an assembly developer? !
For example for embedded systems development.
The main problems are:
1) The work yields very little, because every assembly instruction does very little.
2) Control structures are scarce, you basically have "Jump" and nothing else.
3) The developer will have to decorate a compendium of instructions that only applies to a processor, sometimes apply only to a range of models, so it is a knowledge that gets stale fast.
4) Portability is compromised; copying code from another project that involves another architecture is complicated.
5) In theory a program written in assembly is faster than any other, but this may not be true with new processor models, where your program still works but the instructions do not work the same way as before; anyone who writes compilers learns this well before the processor reaches the market.
Using assembler still makes sense to access special instructions that compilers do not take advantage of. This is the case with some mathematical optimizations, DSP drivers, hardware accelerated encryption, etc.
