>>24
I'm not
>>17, but asm is indeed an easy language to learn, it's simply about knowing the opcodes, how they change the internal states of the machine and the operands used, however of course writting complex applications in asm is a bit more challenging since it's not that easy to maintain, which is why most people usually don't keep large parts of their codebases coded in pure asm. Knowledge of a CPUs opcodes doesn't mean you understand the whole achitecture behind the whole system, or even the CPU itself (for example interrupt management, paging, or how would one go about implementing cross protection level call gates/syscalls).
Learning asm is easy, mastering it and uses it for low-level or optimizations jobs is not as easy. Take brainfuck for example, the opcodes are very simple, but writing real code in it can be quite a challenge. On a more realistic scale, an experienced C programmer shouldn't have much trouble coding in asm if he knows the opcodes and understands how to organize his functions (and their stackframes).