undefined | Better HN

0 pointscaptainmuon4y ago0 comments

If you keep the browser ultra modular, I think it can work. You need to have one component for layout, one for css, one for the DOM, and you can use external libraries for media playback, javascript, networking, and so on.

I think a decent layout or CSS library would be useful outside of a web browser, too.

Then I would also only focus on the subset of websites that are "documents", not "apps". If I could decide, HTML6 would have two profiles: one ultra restricted (maybe no legacy stuff and no cross site scripting) for "documents", and one where you can do all kinds of crazy stuff like "web USB" for "apps". That's not going to happen because Google and Apple like the "open" web as complex and messy as it is, because it gives them total control as you know. But it doesn't stop a browser vendor from building a browser with two engines - your own engine for the majority of documents and chromium for webapps.

0 comments

5 comments · 3 top-level

ya_throw4y ago· 2 in thread

Sounds like a lot of work for moving lightly-formatted text files around. Also, essentially no-one wants it. What people want (whether they know it or not) is the latest shiny to keep themselves distracted.

captainmuonOP4y ago

I don't know a single non-technical person who doesn't complain about web browsers being slow. Part of the problem is that they don't understand the differences between computers and go for the cheapest PC or tablet, but most of it is bloat.

We tried to introduce office 365 company wide for collaboration, but we had a whole plant of 150 employees "mutiny" because they refused to use any of the office web apps because they were too slow.

This slowness is not a fundamental problem, but incidental. The layout calculations of even the most complex websites could be solved by a 10 years old computer instantly. The rendering can be done by a GPU without sweat. Look at how many polygons and shaders games had 10 years ago.

And note I'm not talking about "lightly formatted text files", but 90% of all web sites. News sites, Youtube, Reddit, .... What I'm excluding is Gmail, Office365, anything that uses Vibration, NFC, WebMidi, and other boutiqe features (you could probably add those back as libraries if you need them later). I'd argue that not supporting "apps" is a feature - you'd have to explicity allow them and they'd run in a sandboxed tab.

MichaelBurge4y ago

You could start off targeting developers, who mainly use web browsers to read documentation, HN, bug trackers, code repositories, and other plain documents.

Something for regular people would be many more years of work.

ohgodplsno4y ago

There's a reason why those components aren't modular: it has become impossible for all these components to not be tangled together, unless you're willing to bear the cost of dreadful performance.

qwerty4561274y ago

> Google and Apple like

Apple hates web apps. These are pain in their ass on the way to forcing every app to go through their app store with all the dystopian control it implements.

j / k navigate · click thread line to collapse