10 ms·
Io.js 2.0.0 Released
- randallma 12y agoChangelog: https://github.com/iojs/io.js/blob/7c89c4c7acdaa2035ec42195ade689419209c2fd/CHANGELOG.md https://github.com/iojs/io.js/blob/7c89c4c7acdaa2035ec42195a...
- mcardleliam 12y agoEvery time I wake up it seems like there is a new version of iojs.
- nodejsisbest 12y agoThat's why I always say that Node.js is the best server side JS framework. Pretty stable in terms of never getting updates quickly / etc.
- pmontra 12y agoAnd is that a good thing? You are not forced to update (in another environment, I have customers with Rails apps in production of version 2.3, 3.0, 3.2, 4.0, 4.2) but you have the option to develop with the latest technology. In those Rails examples: I'll start new projects with Rails 4.2 and Ruby 2.2.2 and not with what I had two years ago. In the JS world, I'd start with ES6 and the latest v8, not the old one from node.
- imaginenore 12y agoThat's like saying a 486 CPU is more stable than a modern i7 CPU just because it's slower.
- BinaryIdiot 12y agoNow we just need io.js to merge with node. I feel like I can't use io.js for anything beyond experimentation until the inevitable happens. Edit: Damn that was quickly downvoted. It seems the HN community is more behind io.js than it was a few months ago. I still think node and io.js using the same package manager is simply untenable so I'm just waiting for something to give before I decide to use io.js beyond experimentation.
- cheepin 12y agoWhat is the "inevitable" you are referring to?
- BinaryIdiot 12y agoThe merger of io.js and node. They're using the same package manager which is untenable when API changes occur between the two.
- Cthulhu_ 12y agoI could see them forking the package manager though, if that is the case.
- BinaryIdiot 12y agoBut that would create yet another problem. npm has a lot of infrastructure setup so now you have to duplicate all of this infrastructure, get people to adopt your new package manager that's identical to the old one (except has slightly different module support) and move the community to it (or get them to use it in parallel). I don't think a community of two platforms that are 97% similar with over 145,000 packages can thrive with a fork. Do all 145,000 modules move to the newly forked npm? Do they even have a choice? I love the ideas behind io.js I just don't understand how it can survive on its own unless it can somehow kill node. I can't see both coexisting for long.
- tracker1 12y agoI can't speak for anyone else... but since shortly after the first iojs release, I've been targeting it for all new development. Deploys are moving towards docker based deployment so can, in theory support anything that can be tested on its' own for integration tests. The bigger thing is that security and critical updates are hitting iojs quickly and following semver, they are not hitting node in a timely manner.
- bdcravens 12y ago
- mmcclure 12y agoJust like all statistics, these should be taken with a grain of salt, but I think Github's "pulse" breakdowns between Iojs and Node are pretty sobering. Iojs: 49 authors have pushed 168 commits to master and 572 commits to all branches. On master, 8,474 files have changed and there have been 1,524,012 additions and 708,276 deletions. Node: 30 authors have pushed 5 commits to master and 95 commits to all branches. On master, 10 files have changed and there have been 294 additions and 36 deletions. That's for the last month.
- NhanH 12y agoDid I read the number wrong, or is that an absurd amount of changes (note: I haven't look at the commit myself, as I have no idea how to get all the stats from github interface)? That's about 800000 additional lines of code for 49 developers in a months, or ~16000 LOC for each developer. Unless additions and deletions are counted on a different unit, can anyone knowledgeable explain to me how the numbers are reasonable at all?
- frutiger 12y agoUnless you ask it, git considers file moves to be a complete deletion of the file along with the addition of the file. A good way to tell git to detect renames is to use the similarity flags: `git diff -M60% --shortstat` will consider files 60% similar to be renames.
- deleted 12y ago[deleted]
- lugg 12y agoMost of it is junk find and replace stuff / formatting docs etc. [1] Pulse [2] is just a neat github feature that gives you an overview of a project. LOC will always be a shitty metric for anything. [1] https://github.com/iojs/io.js/commit/56e4255382ad4d2426e034624b41bbe97d18bca0 https://github.com/iojs/io.js/commit/56e4255382ad4d2426e0346... [2] https://github.com/iojs/io.js/pulse https://github.com/iojs/io.js/pulse
- deleted 12y ago[deleted]
- deleted 12y ago[deleted]
- reimertz 12y ago"process.nextTick() performance has been improved by between 2-42% across the benchmark suite, notable because this is heavily used across core (Brian White)" That is pretty amazing.
- brianorwhatever 12y agoShould I be ditching node for io?
- kremlin 12y agoYes, I think so.
- BinaryIdiot 12y agoPersonally I would wait but you can certainly use io.js as you do node. I commented elsewhere in this thread about my whys so I won't be annoying and repeat them here but if you want to experiment or need some bleeding edge performance in some of the areas that io.js is faster (the newer V8 isn't faster in all situations) go for it otherwise I'd stick with node for now.
- jorangreef 12y agoYes
- Joe8Bit 12y agoBeen using it production for a couple months now, no issues. We have a reasonable number of IO.js powered microservices, we've seen anecdotally better performance for some use cases but regressions in none, however we've seen SIGNIFICANTLY cleaner code (ES6 yay!) and a much simplified build (no transpilation to ES5!). Was nervous at first, but now I see no reason to use code Node again.
- k__ 12y agoThere seem to be a few people who like to merge node and IO, but I have the impression most of the community doesn't want to merge. I think node will go down in favor of IO, because they can't keep up.
- tracker1 12y agoI think it's still entirely possible for Node's new org to pretty much adopt iojs's technical committee nearly as-is. There's still no version conflicts. There's a minor support niggle for some internationalization bits in node 0.12's core, but beyond that, there's still a chance. My only thought is that when io.js/node reaches a point for an LTS release, that they do a major bump for the LTS, and another for the ongoing dev... so that #.x.x is LTS. instead of ~#.#.x
- smegel 12y agoIf there wasn't a new cool kid on the block every month making last month's cool kid look like a douche, it just wouldn't be JavaScript.
- TheAceOfHearts 12y agoVery exciting! It's great to see ES6 slowly rolling out as well. I've been using it with babeljs and it's been a blast.
- markthethomas 12y agoCongrats to the io.js team! I know there's lots going on in the node vs. io.js world/debate/comparison/everything, but regardless it's so great to see a team working on an OSS project so well.
- mrinterweb 12y agoJust in case anyone is concerned, as I was, you can reach this site at https://iojs.io/en/index.html https://iojs.io/en/index.html :)
- EazyC 12y agoMan, if there was ever a cool domain name to use the .io TLD it'd be iojs...WHY ARE THEY .ORG!!
- algorithms 12y agoWell .org is pretty much the standard TLD for open source projects. While it would be "cool" to use .io it might confuse some people. It's very common for example that projects have an .org for their Open Source software and .com or other for their business behind it (see wordpress.org vs wordpress.com)
- EazyC 12y agoYa, makes sense. What about all the trendy open source stuff that have the TLD .io as their suffix like socket.io etc? How did the .io trend start anyway?
- mejari 12y agoso they'd be iojs.io?
- silverwind 12y agoThat domain was infact donated recently and is now redirecting to iojs.org.
- secoif 12y agoThe V8 4.2 update adds support for Native Classes in JavaScript: https://github.com/iojs/io.js/issues/1393 https://github.com/iojs/io.js/issues/1393 Significant & controversial.
- dheera 12y agoConfusing name. I just spent a while trying to figure out what this thing is. It should be hereafter forbidden to name anything ".js" unless it actually is a library written IN JavaScript and designed to be used within JavaScript code.
- Ravengenocide 12y ago> io.js is an npm compatible platform originally based on Node.js™. Doesn't that explain it pretty well?
- dheera 12y agoThe first time I read this sentence, I thought it was some kind of I/O library for users of Node. I thought "npm-compatible platform" meant "this is some kind of library that can be installed/added to your project by using npm".
- lucastx 12y agoAlso there is a very interesting language called Io: http://iolanguage.org/ http://iolanguage.org/ I actually thought (just woke up, dizzy) that the news was about the language.
- rsp1984 12y agoExactly. I was too afraid to ask actually and be downvoted and labeled totally uncool. So what is it? I'm still not smarter after reading the FAQ. A "Javascript Platform". Aha. What do I use it for and what problem does it solve for me? I see it's a fork of Node.js. So people use Node.js to write server programs in Javascript, I heard. So is io.js then "competing" with Node.js then? Not going to ask what npm is now...
- Siecje 12y agoNode Package Manager
- thomasfoster96 12y ago
- jpalomaki 12y agoRyan Dahl in 2011 interview: "Hopefully in the next 6 months we'll release a 1.0 version of Node. The idea is to constrain what goes into "core" and not allow it to grow too big - so there will not be endless stream of feature additions. 1.0 will look pretty much like Node does now" http://bostinno.streetwise.co/2011/01/31/node-js-interview-4-questions-with-creator-ryan-dahl/ http://bostinno.streetwise.co/2011/01/31/node-js-interview-4...
- hitekker 12y agoI was at a conference recently and had the privilege of mikeal (@mikeal) explain the differences between io.js and node.js, as well as the future that he and the io.js team saw for node as a whole. All that he articulated at the conference is pretty much what you see on iojs.org. What struck me in particular was how reasonable and level-headed he was about the entire controversy. While it would be very easy to castigate Joyent for their incompetence, mikeal was positive throughout the whole presentation, without having that positivity detract from the mission of io.js (i.e. he said things that were nice, but not empty or hollow.) His fellow, emilyrose (also on github), also seemed like a fairly intelligent person. From that short encounter alone, I would say IO.JS appears have quite to have a healthy community. Here's hoping they can take Node off of Joyent's hands, and merge IO.JS into it.
- alexggordon 12y agoI know I'm coming to this a little late, but I'd be really interested in knowing what the Node creators think is happening with node currently. The current top comment here[0] cites an active community with iojs, and a not so active community with node . However, I can't imagine that the node creators would say that node is stagnant or perfect, so before we start comparing node to IE, has anyone done any kind of reconciliation with the node devs? I understand why iojs forked, but I really hate to see communities get abandoned or go stagnant like this. [0] https://news.ycombinator.com/item?id=9490843#9490962 https://news.ycombinator.com/item?id=9490843#9490962
- jorangreef 12y agoAs far as I understand, the majority of Node core contributors thought it necessary to move Node.js to io.js, and are now active there. io.js is basically the new Node.js, barring the name. It's less a fork, and more a rename, to get control back from Joyent who could have threatened some of the core team over the trademark.