A good post, though I have a couple of minor criticisms:
> Nobody writes assembly code any more, except when they do,
His very first sentence turns out to be the primary assumption of RISC: essentially nobody writes assembly code so don't worry about making that easy, and depend on the HLL compiler to do a lot of heavy lifting. The small amount of assembly is just to boot the processor, boot a process, and some small glue in the OS, and as that stuff is heavily used but almost never written you don't have to worry about alleviating those peoples' suffering.
Oh, and compiler and debugger writers, and he does point out how some of these decisions make things more complex for them!
> CISC had always involved decoding instructions into micro-instructions.
That isn't actually true; into the 60s instructions were implemented in hardware, and the roots of CISC lie there -- essentially some quintessentially CISC instructions (BCD support, string handling, etc) were subroutines implemented in hardware because they were so common and that made the computer easier to sell. (as an aside: back in those days, when the machines had high level languages they were often unique to the vendor or even the specific machine model!)
Then again, even tiny machines like the 8080 that weren't really RISC or CISC had microcode, but that was later.