disabled the chromium sandboxing.
Post by Sam Lanning
I think currently, the biggest problem wrt: electron (or some other
browser-based application platform) is updates. Chrome is very good
at updating itself, if you use electron, you need to create your own
update infrastructure and logic etc...
This is demonstrated / highlighted by a recent twitter
For context, yan (bcrypt) works on the brave browser, which uses
electron (well, more specifically, brave have forked electron and
were providing upstream patches, not sure if they still do that).
So I'm not sure what the current situation is with auto-updating
electron apps, but as i understand it this has been the biggest
sticking point for a while...
there have been discussions on here around this in the past, and on github
using electron to make it into a standalone desktop app would
make this a moot issue! from what I gather, when this project
began, electron was still under heavy development, and
node-webkit was stable but limiting. The chrome.extensions API
was pretty nice to work with in my experience, so it makes sense
it started this way!
The popularity and stability/ecosystem around electron is
possibly a reason chrome apps are being abandoned at this point.
From a quick glance, much of what signal-desktop utilizes from
the chrome API seems to be quite portable to any browser-driven
runtime, such as electron.
Of course, I could be overlooking some glaring critical
dependency on chrome.
There are some features that are native to chrome apps - storage,
notifications, etc that would need to be reworked, but otherwise
it could be kept simple.
A while ago on github I chimed in on a suggestion to move to both
React and Electron - however just moving to electron is whats
most relevant and realistic.
Eventually, we could exploit other features of electron -
multiple windows, more nuanced background processes, other
advantages of using node.js directly.
probably put in a weekend or two on this! I've heard one of the
original core devs is really awesome!
Post by Shankar Kulumani
continue development on the chrome app.
Soon chrome is also deprecating the apps so ows already seems to
be planning another framework for the app.
There are a few Twitter comments and responses on GitHub that
highlight this as well.
Last month, someone [mentioned why] entreaties regarding Firefox are
largely being dismissed. It's not really about market share, but that
it's not a platform that will really support extensive
plugins. In other
words, it's wasted effort.
That said, I'm wondering if we can't get a standalone
desktop client. Or
is that something I haven't noticed?
@wxl | polka.bike
C563 CAC5 8BE1 2F22 A49D
68F6 8B57 A48B C4F2 051A