3 ms·

Comparing to web apps was out of scope, but if I understand you right, I disagree with this. Many apps should not need an active internet connection. You can't

Comparing to web apps was out of scope, but if I understand you right, I disagree with this. Many apps should not need an active internet connection. You can't do local first / offline first. Users don't own their data, need to give up on privacy, and you require more trust of them. Users are always forced to upgrade, and don't control the upgrade process... You also incur recurrent server cost that need to be passed down to your users (as a matter of fact, I suspect that some web apps are an excuse for a subscription where a one-time payment would suffice) You'd have other problems too, like browser compatibility, etc. I don't think "we run remote webapps all day without effort".

keikobadthebad 3y ago
> Comparing to web apps was out of scope "The framework is designed to create desktop applications using web technologies (mainly HTML, CSS and JavaScript, although other technologies such as front-end frameworks and WebAssembly are possible) that are rendered using a version of the Chromium browser engine and a back end using the Node.js runtime environment." https://en.m.wikipedia.org/wiki/Electron_(software_framework) https://en.m.wikipedia.org/wiki/Electron_(software_framework... You can run the 'wep app' backend locally on 127.0.0.1 and no need to deliver a specific browser; use the system one a la cupsd. This would be better than 'electron' scheme and doesn't restrict you from implementing a CRDT or similar to blur the line between on and offline with the system browser the UI either way. > I don't think "we run remote webapps all day without effort". I mean you and I, as users, run other peoples' web apps all day without effort, or installation. Like, eg, hackernews. This has become extremely natural.
- jamager 3y ago
  ah ok, got it