A decade-late attempt to catch up with the JVM. Notice how there's no design here? It's because the web people had no idea this would be necessary and it got bolted on as a reaction to competitors. That is to say, the innovation belongs to plugin vendors, not the web people.
I would have been perfectly happy to be working with the JVM here, except that the JVM as a platform for web-type client stuff died because the user experience was implemented so shoddily.
There was no conspiracy against it. It had its chance. It used to have high install rates. It was placed about as perfectly for success as you could hope to be. If it hadn't failed so miserably at what it set out to do and be (and instead succeeded in a different area), we would be using it now, and living in the utopia you wish for.
As an aside, a lot of your complaints against web technologies make it sound as if there is a cohesive group of people designing something and doing it wrong. Actually it's a much more chaotic process involving a diverse group of people and companies and competing interests. It doesn't guarantee that we end up with the best designs, but such a process has benefits too, and since it's happening in the open, you could actually take part too (assuming you aren't already).
>It doesn't guarantee that we end up with the best designs, but such a process has benefits too, and since it's happening in the open, you could actually take part too (assuming you aren't already).
Unfortunately, what is needed is LESS people participating.