4 ms·
When I read that I had a suspicion that it was going to be electron. It takes some gall to write that heading. Disappointing, 1Password!
by switch007 6y ago
When I read that I had a suspicion that it was going to be electron. It takes some gall to write that heading.
Disappointing, 1Password!
- pjmlp 6y agoI already have a browser installed and WebWidgets support on Gtk and KDE, no need for having a bundled browser with each application. Want to do a native Linux app with Web stack? Easy, do it like in the old days, start a daemon and use the local browser. Naturally this makes it harder, because now they would need to worry about Web standards instead of ChromeOS APIs.
- floatboth 6y agoElectron has nothing to do with ChromeOS. In fact ChromeOS could not run Electron apps until the very recent "Linux app support" that's still not available on all devices AFAIK. (Or developer mode hacks + awkward ways of exposing GUI to Chrome that don't support GPU acceleration.)
- pjmlp 6y agoAnother one that didn't get the message that shipping Chrome as application runtime, with Chrome specific APIs, not available as Web standards, is hardly any different than turning the Web into ChromeOS.
- floatboth 6y agoYour post above reads like an incorrect factual statement, not vague message. Either way, Electron's APIs for using native parts of the app from the web part are purely Electron's and DO NOT exist in other Chromium based products.