: Every MCU has it's own assembly language, more or less. Though microcontrollers from the same manufacturer tend to have very similar asm instructions.
: Since I don't know much about x86, I'm not sure if I'm able to make the comparison, but I think there is a rather large difference. If you are interested, here is the manual for a 6800:ish (Motorola) 16-bit MCU (HCS12):
: Should be as far from Intel as you can get, hopefully
Of course there are lots of other platforms, but is there any point in learning asm for some embedded system with completely different instruction sets and architectural designs just to get a bit of insight of other, different things? Not in my opinion.
You`ll find loads of code for x86 on the web, but other platforms tend to be rather short on asm code (exeptions include some more popular embedded platforms where asm is applied more often, like Z80 or 68k). Also, you will need the processor itself for which to code for in the first place.
Furthermore, learning different architetures can be quite a fuss, all the mnemonics are criptic anyway.
We have reccommended assembly to talhanasir in order to get him to understand how C/C++ programs get compiled. This would be extremely useful for debugging, but debugging for embedded systems is quite a deed, if possible at all. Optimisation is secondary, because modern C++ compilers can compile good code.
Besides, I was talking about MOST programmers, not ALL programmers so you can`t say that I made programmers and PC programmers equal. I assumed talhanasir to be in the majority, but if he wants to develop for some other platform, I`m certainly not stopping him