3 ms·

Couldn't agree more. I got butterflies when thinking about node-webkit with gecko instead of webkit, but reading through the post just made me really disappoint

Couldn't agree more. I got butterflies when thinking about node-webkit with gecko instead of webkit, but reading through the post just made me really disappointed. The reason I really want something like node-firefox is the build process for firefox is so much easier than webkit, and if I make a desktop app that I want people to be able to build from source node-webkit is such a huge beast to compile. I'm basically stuck with the binary versions, which is not the way to go for software that does crypto. Does anyone know how hard it would be to make a real node-firefox (as in, FF version of node-webkit)? Why is chrome the go-to for all the web-app-as-desktop-app frameworks?

realityking 12y ago
In the case of node-webkit they give you access to both the Web platform and node APIs. That's possible because both projects use V8, so with a bit of twisting they can be relatively easily integrated into one. (Incidentally, this is why they're using io.js, the outdated V8 version in node made things more difficult) If you wanted node-gecko you'd either need to fuse V8 to gecko or reimplement or create a wrapper around spidermonkey emulating the V8 API. That's a lot of work.