4 ms·

This isn't particularly surprising, NW.js (previously called node-webkit) switched to IO.js as well. Edit: to clarify, this is relevant because both Atom and N

This isn't particularly surprising, NW.js (previously called node-webkit) switched to IO.js as well. Edit: to clarify, this is relevant because both Atom and NW.js use a webkit shell.

teleclimber 12y ago
Oddly enough Atom-Shell has apparently not made the switch to IO.js? No mention of it in the releases page. https://github.com/atom/atom-shell/releases https://github.com/atom/atom-shell/releases
- thedaniel 12y ago
  atom-shell absolutely has made the switch to io.js, that's where Atom's node comes from.
  - teleclimber 12y ago
    Huh, I just downloaded the latest atom-shell and ran a hello-world that dumps the "node" version and it says v1.0.0-pre. That sounds like IO.js alright. Why then would they still refer to "Node" in the release notes, all the way up to the most recent version?? "Fix initializing node integration in the webview when the page in it navigates."[1] https://github.com/atom/atom-shell/releases https://github.com/atom/atom-shell/releases
    - jipiboily 12y ago
      It might be about a DOM node, not the Node project.
    - xpaulbettsx 12y ago
      That's just a typo, it indeed does refer to io.js integration in WebView tags.
xpaulbettsx 12y ago
To be pedantic, Atom Shell and NW.js are both based on Chromium (Blink), not WebKit