3 ms·
I'm really happy with the effort of "compiling" NodeJS to native binary. What I'm looking forward to is lightweight electron that will allow us to use the nati
by drinchev 9y ago
I'm really happy with the effort of "compiling" NodeJS to native binary.
What I'm looking forward to is lightweight electron that will allow us to use the native browser-engine for each platform.
QT/GTK for Linux, WebkitView for macOS, Edge for Windows.
Hope the effort of node-compiler, zeit/pkg will be beneficial for the future of desktop apps.
- dchest 9y agoHere's proof of concept from yesterday: https://news.ycombinator.com/item?id=14260755 https://news.ycombinator.com/item?id=14260755
- statictype 9y agoOne major advantage of Electron is not having to deal with browser compatibility issues - you write your code against exactly one runtime (sure, you may need platform specific flags for things - but no risk of the runtime changing/breaking after you deploy) Leveraging existing OS engine will reduce file size but at the cost of not having a stable and known platform that your code will run on.
- drinchev 9y agoThese days fixing those issues should not be a big deal. Having all those polyfills / babel / webpack tools you can be quite safe about your app. Nevertheless having a nice test suite also makes a benefit.
- tracker1 9y agoI can't help but think that electron could eventually become similar to Adobe Air (except actually open), where the main runtime is/can be installed separately, so multiple apps can share a runtime.
- h1d 9y agoPlease don't ever do this. No one likes installing separate system library of some sort, even multiple versions of it besides downloading the app. Besides what's the point when most people would only use just a few Electron apps anyway. App developers also have to ask users to download versions between this and that system library only causing confusions for users.