3 ms·
You're not wrong on electron: this tech allow devs to be lazy and we all know that when we are allowed to be lazy, most of the time we are. That said, electron
by orwin 9y ago
You're not wrong on electron: this tech allow devs to be lazy and we all know that when we are allowed to be lazy, most of the time we are.
That said, electron can have a small fingerprint if the dev team is carefull/good enough, and is hte best option when your app have to be able to read HTML (and copy HTML formatted string). To me, an email client is a good way to use electron for an app.
- sametmax 9y agoAnd let's not forget that thunderbird ui itself is rendered using gecko.
- lallysingh 9y agoRe: lazy: some would call that get more stuff done faster and cheaper.
- dspillett 9y agoI prefer to use the word "efficient"! Or for advanced situations "selectively efficient" - using something other than Electron for an app that is intended to be cross-platform because [insert-alternative-here] is smaller/faster/other may be an example of premature optimisation and using something else (especially where that involves learning something else) could mean trading off elsewhere.
- c-smile 9y ago"this tech allow devs to be lazy" Not just Electron but Sciter too in that sense. "electron can have a small fingerprint if the dev team is carefull/good enough" Only to some extent. You will have two separate process (at least) in any case and so two sets of the same system libraries loaded in them, IPC between them, etc. Main task of browser engine is to provide safe browsing experience. Presenting HTML is only second its task and so browser based UI will always be sub-optimal (at best).