Re:Io.js 2.0.0 Released
by davedx on Tuesday May 05, 2015 @11:18AM
(#9492949)
Which breaking changes are there in io.js? I'm just curious, not been following it closely; but AngularJS 2.0 is a completely different API. You can't "migrate" an Angular 1 project to Angular 2, you need to rewrite it. That's understandably scary and horrible for some people.
[ Parent
| on HN ]
For the most part, almost all JavaScript code and modules will run the same under io.js as node.js. The primary point of breakage is binary modules. io.js is constantly upgrading their V8 bindings, so binary modules need to be updated much more frequently than with node.js.
Re:Io.js 2.0.0 Released
by jorangreef on Tuesday May 05, 2015 @01:31PM
(#9493745)
It's more a case of dealing with the legacy problem of node.js never having upgraded V8 as often as they should have.
> 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.
With that much change in such a short time, it would be extremely optimistic to think something didnt break. If I had a lot of production code depending on node, those numbers would scare the crap out of me.
You can absolutely migrate angular 1 to angular 2. Following good practices (i.e not having 4k line controllers) that were place since its inception only makes that migration easier.
Re:Io.js 2.0.0 Released
by heydenberk on Tuesday May 05, 2015 @01:12PM
(#9493627)
Server code is much easier to test with unit and integration tests than UI code which is part of the reason that people dislike breaking changes in UI frameworks more than in other kinds of libraries.