You are in your bubble indeed.<p>- Sure, <i>my</i> computer has 16GB. The computer I develop on, plus run a couple VMs, containers, etc. That is not the case for the common user, who has to make do with less. This is especially palpable on mobile, with less RAM, fewer cores and more throttling.<p>- And those 16 GB? Nope, I do not intend to squander them <i>on your app</i>, and neither do the users. We <i>use</i> the computers, y'know. Perhaps to run an IDE, perhaps to watch a movie, perhaps to make a spreadsheet, but most apps are an <i>addition</i> to the main task. This is the epitome of arrogance: "you have X of resource, AND IT'S ALL MINE!" And you have 30 such intents-to-munch competing.<p>- Most of the time, it's a massive overkill: case in point, Slack: 2 billion bytes of RAM to show a chatroom, i.e. a few thousand bytes of mostly text? EXCUSE ME?!<p>- Apart from that, and the overhead of bundling and running a separate browser for each app, with all the issues it entails, the <i>theoretical</i> idea of desktop-web apps is quite appealing, as opposed to its actual implementations. For prototypes, excellent; don't shove prototypes to production though, that passes the buck onto end users.<p>I have built a major app in HTA (way before Electron, similar in principle). 1*, would not build again: easy to build, and that's about it.