Earlier quoted context omitted.
How about not developing applications in the browser? Its about linked documents. Not angular-17 MVVM async session persistence in indexdb with websql and asm.js rendering webgl for a spinning teapot.
OK. So you get your 'document only' internet. Where do we put all the other stuff? I have a bunch of 'non-document' websites that are essential to me now. What happens under your new regime? Someone reimplements them all as native apps? The point I'm making is just because your internet is document-only please don't assume mine or other people's are.
Every web app is written in perl/php, therefore we will keep using perl/php. - What will you do, rewrite the apps? internet != web.
This cludge of in-browser tech everyone is pursuing already comes with so much suffering for the developer. But the enthusiasm to embrace garbage like religion is just unbelievable. (yeah js everything, spotify lol)
I think the current webapp tech stack is not doing our generation justice. Yes google has very strong interests in maintaining status quo since it dominates it and so do many other giants. But good, user friendly and maintainable software looks different.
Why not break the completely misused model of documents for apps ? there is no document semantics in 1000x elements riddled with js callbacks.
But dont let my cynicism annoy you, its the resignation talking. Imagine what cool tech we would have if something was started in the 90s (no, not java applets) and was all grown up now.
But every big company is now a walled garden provider. Just think about UI toolkits, would spotify be in Chromeframe otherwise?.