spoiler, re: methodology 

@sir How can we go back to something simpler. Will we be able to reboot it ? How one reboots such beast ? Or maybe have a secondary "browser" for the "new" era of simpler mecanisms ?

@themartylake I think we need a new web browser which pledges to approach the web problem on the grounds of simplicity, stability, performance, and security, and declares a subset of the web standards as blessed and implements only those.

@sir @themartylake Does it make sense to build a new web browser?
It's very tempting to say that the vast majority of the HTTP+TLS+HTML+JS+CSS web has been hijacked by either dangerous or outright malicious actors, and they should be left to their own devices (pun partially intended).

Maybe it's time for a retrospective and an exploration of alternatives.

@e @themartylake I wouldn't invite JavaScript. I don't think that the alternatives to HTML are compelling for the same use-cases

@sir @themartylake Which particular use cases are you considering?
@sir @themartylake I guess I fail to see the end goal here.

@e @sir The problem with a full reboot is that the web is also a huge collection of tools that maybe can be repurposed if it is not a reboot, but just a subset. Some sort of "strict-web" ? like strict-cpp ? gist.github.com/bkaradzic/2e39

@themartylake @sir Here's a radically different take:
The foundation for the last major iteration of "The Web" has already been laid: Canvas/WebGL, and WebAssembly are supported by all major browsers.

With that in mind, we should get it over with and excise the rest of the WWW stack from the browser engines. Define a format to stream raw webasm to the browser, to be executed in a secure enclave (far out of reach from normal user-mode programs) and then displayed on the canvas, which now covers the full tab.

There you go, Facebook/Apple/Amazon/Netflix/Google. No more pesky HTML semantics, or ad blocking, or people scraping your data, or anything really. You can do whatever you want now, completely impervious. The stakeholders will surely want to introduce some sort of tamper protection as well, and then we're done.

The worst (most profitable) of the web has come to pass.

This is the end-game: dumb terminals with just enough power to handle their own UI, while making sure nobody else (users included) can poke around inside the apps.

Long post 

@sir It seems that nobody remembers that less is more. Websites are being built with technologies that are insecure and inefficient. Just wish there was something that could be done about it, but unless you have the support of a huge company and multiple teams behind you, it won't happen.

@inferiormartin @sir inefficient, yes, but insecure? i don't think you'd want to go ten or fifteen years back in web security

@leip4Ier @sir That wasn't my point though. While things have improved in some regards, others have gotten worse. Programs that are simpler have less angles prone to attack. I think npm is a very good example of this. It has a comprised library every damn day.

@sir
I completely agree with your statements.
I would love a browser that has only the bare minimum features and that they stop adding stuff everyday.

Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!