Jonathan Blow

Riho insinuated that since some things are more complex than others, bad performance is inevitable, or even if you optimize something slow frameworks are the default, or something. Argument by vague trend, noncentral. J asked straightforward questions that weren't really answered

He rightfully pointed out that the web is intrinsically more complex than one-size-fits-one, non-accessible, machine-opaque game UIs. “J” just chewed his lip on “I don’t get why that’s hard” which translated “I don’t get it”

Clearly never read the spec, knows nothing about browsers, ignorant. Which isn’t generally a position I prefer to condescend from

You haven't understood what I am saying. "The spec" as it currently exists is a fundamentally bad idea about how to solve this class of problem. The results are obviously terrible. People should observe and learn from this, but somehow don't.

The basic ideas behind how these things are architected are rotten at multiple levels. The proof is that the results completely suck compared to what is being done in other fields. This is clear unless your paycheck depends on not noticing it.

Yes I too would prefer if the web didn't have decades of legacy.

So now you are saying things are not good but you're a powerless engineer who can't do anything? That seems inconsistent with your previous story that things are actually great. Which is it?

And the issue isn't exactly that there are "decades of legacy", it's that there are decades of stupid legacy that do a bad job of solving the wrong problems, and that make it tremendously harder to do things than it actually should be. Important to include that part.