2 ms·
On an economical perspective, i wish we had more choice than between Google, Mozilla and Brave, all of which have shown to be corrupt and care little about user
by southerntofu 5y ago
On an economical perspective, i wish we had more choice than between Google, Mozilla and Brave, all of which have shown to be corrupt and care little about users. I'm sure a popular browser could receive tons of donations if it was based on such model and stopped remunerating execs/managers (or did away with those vampires entirely).
On a technical perspective, i'd like a modern document browser, not a webapp engine. I can appreciate a cross-platform app runtime (WASI project sounds good), but running random code from every website i visit has only downsides for me. I feel like the useful aspects of the web are declarative (HTML/CSS) that the browser is free to ignore/override to provide better UX, and i'm sad innovation in declarative web seems to have entirely stopped after HTML5 shipped <audio> and <video> (and a few others).
Why can't login/logout, drag & drop, background polling for dynamic content updates, and content "tabs" in page (not based on :checked hack) be part of the HTML spec?
<section reload="2m" src="https://foobar/newarticles.rss https://foobar/newarticles.rss" schema="https://foobar/template.html https://foobar/template.html">
^ my browser would let me opt-in/opt-out of background updates and/or change the frequency... which i can't control with crappy JS applets that just make tons of background activity and break in the most unhelpful ways when wifi/VPN/tor looses connectivity
All in all, declarative formats empower users, whereas imperative formats (ECMAScript) empower content producers and advertisers. I wish we had a sort of web users union doing R&D on such topics and employing people to work on user-respecting tech.