But of course, working with SAX parsing is yet another, very different, bag of snakes.

I still hope that json parsing had the same support for stream processing as XML (I know that there are existing solutions for that, but it's much less common than in the XML world)

Add far as I van remember, you can't access the high/low 8 bits of si, di, sp. ip isn't accessible directly at all.

The ancestry of x86 can actually be traced back to 8 bit cpus - the high/low bits of registers are remenants of an even older arch - but I'm not sure about that from the top of my head.

I think most of the "weird" choices mentioned there boil down to limitations that seem absurd right now, but were real constraints - x87 stack can probably traced back to exposing minimal interface to the host processor - 1 register instead of 8 can save quite a few data line - although a multiplexer can probably solve this - so just a wild guess. MMX probably reused the register file of x87 to save die space.

[0] https://curl.se/dev/vuln-disclosure.html

[1] https://curl.se/docs/bugbounty.html

Seems like a really cool technology, though.

I wonder if anyone else got the same response, or it's just me.

> includes both a human and a computer—and “surprisingly,

It was eventually killed because Apple decided it won't support it on the iPhone.

This is one hell of a rabbit hole...

Like you said, you need to be careful, but you better be prepared to pay dearly (or manage without) for your mistakes...