AFAIK browsers are popular because they load apps quickly and without an install step. While native apps let you choose your stack. An OS based on IPFS would load big apps quickly thanks to caching, the install step would go away because there is no difference between remote files and local ones and its still an OS so the app can be written in C or any other language built on top of it.
If your first thought is that desire for control is a niche thing, an instance of power users projecting their biases onto the rest of the world and not a concern for some mythical "everyman", you are wrong. Because those normal folk are exactly why Excel even gets a mention.
> If your first thought is that desire for control is a niche thing, an instance of power users projecting their biases onto the rest of the world and not a concern for some mythical "everyman", you are wrong.
Evidence? Sales numbers tend to prove the opposite. It's the whole reason the apple ecosystem makes as much money as it does: it just works and it looks good doing it. Most people don't enjoy having to spend any time on getting anything to work or customizing anything to their liking. They just want it to do what it's supposed to do then go back to whatever it is they find more important.
Now, could a zero-install network of apps kill the browser? I'm not so sure. Developing native apps is a royal pain in the ass right now. But, if something like QML were to get a lot better and easier to use, it could take a dent out of the single page application market.
Well that's great, because those aren't words I ever said. The first person to start talking about customizing things is you.
I'm not going to be nudged into mounting a defense for an argument that I never tried to make.
> Superior scripting language
We use Python - on the client and on the server (with rich RPC between the two).
> Steal ideas from GUI-focused languages and toolkits
The biggest such idea is that most layouts should be done visually - Visual Basic had this right, and we've been moving backwards ever since. (The web has three, usually four intermediate representations you have to think through to edit your appearance: Template (->substitution->) HTML (->parsing->) DOM (->CSS render->) visual layout)
https://cx.codaxy.com/fiddle/?f=JHuzRB1C https://cx.codaxy.com/fiddle/?f=vwyHzOO1 https://cx.codaxy.com/docs/
[1] https://www.microsoft.com/en-us/research/publication/the-mul...
I want someone, probably Google since they own both a major browser and some of the most popular web applications, to re-invent the entire stack. Steal ideas from GUI-focused languages and toolkits, like QML, Swift, AppKit, etc. Lets pull in a superior scripting language like Lua and widget-layout framework like Qt, and support it natively and securely in the browser, building on everything we've learned in the last 20 years of creating web applications.