> Side effect is that the next administration gets shitty economic news.
Doesn't this analysis assume that the 2017 administration expected to lose the 2020 election?
I'm genuinely curious. What would have happened if Donald Trump had won the 2020 election? Do you think that the 2022 changes would still have come into effect, or do you think there would have been an effort to change them?
The software security community has a subsection that focuses on the security of compiled binaries, where understanding assembly has many uses. These uses include binary reverse engineering and proof-of-concept exploit development to demonstrate the severity of a vulnerability.
If these do sound interesting to you, I'd recommend looking into capture the flag (CTF) competitions, and trying reverse engineering or binary exploitation (pwn) challenges. PicoCTF [1] is an entry-level platform that hosts challenges and has references to learning resources - I believe there's a sequence on assembly in the learning resources.
Aside, I also find it useful to know assembly when debugging C/C++ code, as others have suggested.
In a 64 bit register, e.g., RAX, AL refers to the lowest 8 bits [0-7] and AH refers to the next 8 bits [8-15].
Together, AX refers to bits [0-15]. EAX refers to [0-31].
It's counterintuitive (or at least, inconsistent) that we have a name for bits [8-15] but not for [16-31] or [32-63]. My fuzzy understanding is that this came about from legacy decisions.
Doesn't this analysis assume that the 2017 administration expected to lose the 2020 election?
I'm genuinely curious. What would have happened if Donald Trump had won the 2020 election? Do you think that the 2022 changes would still have come into effect, or do you think there would have been an effort to change them?