Jonathan Blow

have to engage in endless hacks that almost but don't quite solve the problem, like everyone does today.

Eh, that'd just make it harder to make apps and require more experience to make something good. I think it's too hard to make good apps as it is, even with a perfect understanding of the platform. I'd want it be easier to make good experiences.

Also the only good part (as far as I'm concerned) of DOM, is that it's a common vocabulary between a lot of people and therefore standards can be enforced and promoted. If everyone is flying a custom display tree impl. it'll be even harder to do stuff like screen readers, for ex.

Which people neglect as it is, even with the standards. But at the very least people are forced to use image tags for images for example (to an extent). Code editors can even warn of missing alt descriptions on images.

That's fine, I am not going to argue with you about this any more. I was under the impression that you actually were interested in improving the situation, but you seem to have this mindset that the current situation is the best possible way to do what we have,

and that anything else is not possibly better, because tautologically that's how it is. If you want to live in the ruins of the precursor civilization, go ahead and do that, but that is not my jam.

I see why you'd get that impression, but nothing could be further from the truth. I'm only trying to offer insight into why the current situation is what it is, and why it isn't because all web devs are imbeciles that don't know anything about computers.

There are an infinite number of ways to implement the set of functionality that we want. What we have now is does not supply that functionality particularly well, as it often breaks and is very slow and it is actually very hard to make things, as evidenced by the number