I know this sounds bad, but maybe this is a blessing in disguise. Necessity is the mother of invention and maybe browser technology should be funded by governments instead of privately owned advertising megacorps?
I know this sounds bad, but maybe this is a blessing in disguise. Necessity is the mother of invention and maybe browser technology should be funded by governments instead of privately owned advertising megacorps?
Well, I do think you’re wrong about quite a lot of that. So yeah that is in fact controversial. Upvoted.
But I agree websites are a bloated mess that shouldn’t be made on a giant javascript stack of unreadable unmaintainable garbage. It’d be cool if we got something more like applets. But then we’d have to design a framework that operates in a sandbox and is limited to only functions that are safe to perform on your computer without trusting the author and make it easy to write so developers can build it and… we’re back at html+css+javascript.
I think the big thing we need to do is fully replace javascript.
Have a look at Gemini and the Gemini capsules. Seems more like what a browser should be, in my opinion.
i know i’m in the minority here so i’m not going to bury myself in this hole, but i do think those are addressable problems. many of them have been addressed. replacing Javascript is exactly what i’m talking about.
Isn’t that what wasm kinda is?
not really. using WASM as your full stack for your front end is just adding to the complexity and jank. WASM is there for compute heavy stuff. you can use it that way if you want.
there may be a little angst from reading and rereading the “Max-Age” portion of the cookie RFC that caused this trauma