3 ms·
Ok, I normally find myself disagreeing with HN every time Electron comes up. Basically, I think the upsides are worth the size and performance tradeoffs. Howev
by kristiandupont 9y ago
Ok, I normally find myself disagreeing with HN every time Electron comes up. Basically, I think the upsides are worth the size and performance tradeoffs.
However, this seems to be almost an entire server deploy as well as a complete renderer all in one package. That does seem excessive to me for a desktop app.
- ygra 9y agoAren't there Electron applications that effectively bundle node.js as well? Isn't that kind of the same?
- dspillett 9y agoAll Electron apps do - that is what the Electron framework is: a bundle of Chromium for the front-end and Node for the back-end (where here front/back are UI/internals rather than client/server as they are in an online web application). See https://en.wikipedia.org/wiki/Electron_(software_framework) https://en.wikipedia.org/wiki/Electron_(software_framework) along with the official docs (though the official docs don't state this construction quite as plainly, it doesn't hide the fact).
- romanovcode 9y agoNode.js does the same on "standard" electron apps. What's your point here? This could actually be faster since C# is faster language than Node.
- shakna 9y ago> However, this seems to be almost an entire server deploy as well as a complete renderer all in one package. That does seem excessive to me for a desktop app. That's precisely what Electron is. So what's the difference if you're okay with one?
- kristiandupont 9y agoDoes this not include node as well as .net core?
- shakna 9y agoElectron itself includes node. That's not a difference.
- deleted 9y ago[deleted]