💾 Archived View for bbs.geminispace.org › u › ResetReboot › 15464 captured on 2024-03-21 at 19:19:59. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Re: "Which parts of the web want saving? Which can we do without?"
3- Overcomplicated system to develop: Try to start a new JS application. Do a simple hello world. You have a lot of frameworks (phased out in mere months!) with a lot of dependencies and requirements. With other programming languages, you can get the compiler, create your hello world and in a minute, you are up and running. There's a lot of well seasoned developers that sigh and reach to see how to start a new JS project.
4- (And this is a personal take!) Starting your base on a language that was only thought to be a glue with Java applets and make a couple nice effects. Then drop a ton of patches to make it more usable.
Mar 02 · 3 weeks ago
☕️ tenno-seremel · Mar 19 at 17:23:
I’m with no-scripters. Once you allow scripting it is only a matter of time before it will be extended. Exactly as it already happened. Forms, which can be validated client-side, should stay, though, so every website didn't have to do things this one had to do. And they should be useable without spending lots of time to drag them to present times.
btw there is now this new technology called nextjs which runs js only in backend and only gives the browser prerendered html and css but i doubt corporations will give up browser side scriytss, they need their tracking scripts in your machine.
Which parts of the web want saving? Which can we do without? — Let’s have an unrealistic hypothetical here. Suppose the http web were replaced entirely by a new protocol (or maybe set of protocols?) which allowed for client side scripting, unrestricted styling, and all the other aspects of the web which make it distinct. Except this time, everything was being built from scratch, with person-first values in mind, like privacy, accessibility, ease of use, etc. The designers of this protocol are...