3 ms·
It's the standard for packaging "web applications" to run natively, and the path of least resistance for doing the same with code compiled to WASM. Also VS cod
by krapp 8y ago
It's the standard for packaging "web applications" to run natively, and the path of least resistance for doing the same with code compiled to WASM.
Also VS code runs on Electron, so it's hardly uncommon.
- pjmlp 8y agoThat is called PWA. Electron apps are as native as PWAs, with the caveat that they bring a 300 MB runtime alongside with them. I bet there are still more Swing applications in production than VSCode users. That doesn't make JAR a de facto packing format.
- krapp 8y agoThe point is that existing solutions in practice, however bad they might be, will always beat better solutions which only exist in theory. Electron apps (or, fine, PWAs) will become the standard model for WASM development because that model already exists, and is what developers will most readily use... and because most of the interest in WASM comes from the web development community. By the time something better comes along, it will have to fight against the network effects.
- pjmlp 8y agoElectron is not the same thing as PWAs. I don't need a 300 MB pro application. There is already a perfectly fine browser on my system. Actually four of them.
- Fire-Dragon-DoL 8y agoElectron has a lot more features than PWA and we don't want more features in browser because of security. The result is, we need electron and will keep using it for native apps
- imtringued 8y agoThat would be perfectly okay if the electron developers cared even just a little bit about memory consumption. Last time I checked there were major memory leak issues related to caching (contrary to popular belief caching things that are never accessed again doesn't increase performance).
- pjmlp 8y agoI surely don't need Electron and plan to only use it on the few cases where I don't really have an option, where a proper Web app or an actual native application aren't available as alternative.