5 ms·
The article mentions using Electron or NW.js if you want to continue building apps on web technologies that need deeper platform access. Is there a reason that
by jwmerrill 10y ago
The article mentions using Electron or NW.js if you want to continue building apps on web technologies that need deeper platform access.
Is there a reason that those are worse options than Chrome apps?
- WayneBro 10y agoEach Electron/NW.js app will be packaged with a whole huge runtime. It's not all bad - there's more freedom with these.
- tdicola 10y agoIt's possible but it's not an easy switch. And god help you if you have to mix native code with Electron. Getting a node-gyp toolchain spun up on Windows is a complete and total nightmare. Add Electron and its very specific version of Node into the mix (which totally confused node-gyp) and it's really awful.
- xpaulbettsx 10y agoNah, it's not that hard, not sure why you had so much trouble Source: Have written many many Electron node modules
- comex 10y agoThere's also the alternative of switching to a Chrome extension, no?
- deno 10y agoDifferent sets of APIs[1]. For example Socket, USB are only App APIs. Though I guess they could roll app APIs into extensions… hopefully. Socket API especially.
- mlsarecmg 10y agoIt used to be hard, but when you have tried it last time? These days its as simple as hitting. npm install --global node-gyp npm install --global --production windows-build-tools
- ArmandGrillet 10y agoOnly Chrome apps work on Chrome OS and developing a Chrome app is way easier: Chrome takes care of the back-end and Google offers an app store.