11 ms·
Atom now using Io.js
- luisrudge 12y agoplus 6to5 support! :)
- agmcleod 12y agoAny idea if that would mean auto compilation for your own files in a project? Or is it more for plugins and such?
- dmnd 12y agoIt's for plugins: https://github.com/atom/atom/pull/5299 https://github.com/atom/atom/pull/5299
- mmebane 12y agoI'm curious as to how they will handle 6to5 versioning. 6to5 seems to be very much in a "move fast and break things" stage, and I'm not sure that's going to change any time soon.
- jbrooksuk 12y agoWhat does this mean for Atom? Is it faster? Is the compiled size now smaller?
- kenperkins 12y agoMost likely it means that there's a newer V8 involved. Otherwise there's not a tremendous delta.
- proksoup 12y agoThis is bigger news for io.js than it is for atom. <<< I think is the lede.
- Fishrock123 12y agoYes. It is arguably larger news for io.js. However, that io.js ships with v8 4.1 is quite a large step ahead for dependants, not just for language features, but also under-the-hood stability and performance. Of course, there is also everything that node 0.11.x has, plus a release schedule to match Atom's own release cadence. :)
- vacri 12y agoio.js also ships with the node.js active core developers...
- deleted 12y ago[deleted]
- kikki 12y agoThis is interesting, and a very big business move to make the switch. Does this say something for the future of Node?
- xasos 12y agoI though the whole point of io.js was that they would work on the project faster than Node, but eventually merge back into Node once Joyent became more transparent. The Node release cycle was pretty slow and they had some dispute with the contributors (top 5 original Node contributors now working on io.js)
- cpeterso 12y agoWhy would the io.js team bother merging their changes "upstream" to Node? io.js has momentum and mindshare.
- Wintamute 12y agoThey publicly stated they will merge back in upstream eventually all being well. They're doing it for the good of Node.js, not to create a rift and divide the community's efforts.
- mcantelon 12y agoIIRC the Node Forward initiative was more explicitly focussed on merging back than io.js is. The subtext of io.js seems to be "we'll move forward with or without Node moving foward with us".
- xasos 12y agoYup. Also because Joyent asked that Node Forward not use the "node" term, even though it was in public domain a lot longet than Joyent's been around.
- blacktulip 12y ago
- sigzero 12y agoUntil they fix the 2MB limitation on editing files. No way.
- cordite 12y agoOr syntax highlighting breaking because some code you've been given has some 8K-long regex on one line in the middle.
- VieElm 12y agoRegular expressions are not the way to do syntax highlighting yet many of the popular editors do it this way. Create a super huge string in vim, textmate or sublime text and watch it blow up. Then try it in Xcode or Intellij and see that there is no problem. The reason for Xcode and Intellij's fast syntax highlighting is because these do not use regular expressions, they use a lexer. They're examining the text one character at a time with some amount of forward and backward looking state and building the syntax highlighting and smart completion/features that way. As long as your editor is using regular expressions for syntax highlighting this will be a problem for you.
- thesz 12y agoLexing IS regular expressipn matching (except for some esoteric features like Haskell's nrsted comments). Difference is in the handling. As a matter of fact, Visual Studio uses semantic analysis - classes show differently than other identifiers.
- deleted 12y ago[deleted]
- cordite 12y agoIt can be, it can also be a context free grammar, which is 'higher' than a state machine (or regular expression)
- 12y ago
- dshankar 12y agoThis 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 agoOddly 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 agoatom-shell absolutely has made the switch to io.js, that's where Atom's node comes from.
- teleclimber 12y agoHuh, 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 agoIt might be about a DOM node, not the Node project.
- xpaulbettsx 12y agoThat's just a typo, it indeed does refer to io.js integration in WebView tags.
- xpaulbettsx 12y agoTo be pedantic, Atom Shell and NW.js are both based on Chromium (Blink), not WebKit
- juddlyon 12y agoFor those of you who like me who aren't sure what this is about: Atom - text editor from Github, Io.js - node.js fork.
- sanderjd 12y agoAh, thanks, I forgot that was the name of the fork and was definitely puzzled.
- jug5 12y agoThe official name is io.js, which should never be capitalized, especially not at the start of a sentence, unless it is being displayed in a location that is customarily all-caps (such as the title of man pages).
- joshstrange 12y agoThis is good news but I'm a little confused, if Io.js supports ES6 why do you need 6to5?
- netcraft 12y agoES6 support is not a binary thing. IO.js has a newer version of V8 that supports more ES6 features than node.js's V8 version, but its not even close to all of ES6. to 6to5 shims the rest of the ES6 featureset. see here for more info: http://kangax.github.io/compat-table/es6/ http://kangax.github.io/compat-table/es6/
- joshstrange 12y agoThank you for this! I was a little confused.
- dreen 12y agoif i read this correctly, even 6to5 supports 77% of ES6, which is interesting. too bad its taking so long, i cant wait until full support comes to browsers
- Touche 12y agoThis doesn't explain it, why do you need to compile ES6 at run-time? Plugin authors should compile before distributing. This would annoy me as a user, I don't care that you really want the await/async feature. ES5 is not that bad. It's not like the difference between Lua and Vimscript. Just use ES5 or compile your ES6 prior to distributing.
- jtth 12y agoWhy would I ever use a text editor that uses even node.js, let alone some even newer thing? I don't understand how people can commit to such a thing.
- Hapa 12y agoYou might use it if you are familiar with javascript as many people are. It makes creating packages for many people possible.
- jackweirdy 12y agoBecause it’s a text editor, not a child. If you don’t like it you can close it and the world will keep on turning.
- crucialfelix 12y agoI was just wondering today when this might happen. specifically because I want to use generators in a plugin (supercollider ide). great job guys !
- jbeja 12y agoWho cares? Is going to be slow an unusable non the less.
- visarga 12y ago90% of my work is on remote files by SFTP/SSH. How's that working in Atom?