4 ms·

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 t

• MichaelBurge 5y 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.
• captainmuon 5y 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.