4 ms·
> We are done making breaking changes at the Node.js layer. If your > program runs today, we're doing everything we can to make sure that it > will run next
by leetrout 13y ago
> We are done making breaking changes at the Node.js layer. If your
> program runs today, we're doing everything we can to make sure that it
> will run next year, albeit faster and more reliably.
I've yet to devote any significant amount of time to developing on Node but this is a big +1 for more serious consideration.
My memory is fuzzy (this was well over a year ago) but I remember building an app in express and it being completely broken by updates a very short time later (along with a good number of other modules that hadn't been updated either).
Anyone venture out a guess/opinion on how many things in userland will stabilize because of this? (Or perhaps things already have- I don't hear as many complaints about express' api changing lately).
- treeform 13y agoI remember that time too. Most of the modules I use are pretty stable now, which is nice.
- driverdan 13y agoUserland has become a lot more stable over the past year or two as projects have matured. A lot of popular projects (like express) went through rewrites with breaking changes.
- SimHacker 13y agoDidn't UserLand make Frontier? (It's a Dave Winer joke -- ha ha!)
- mattyod 13y agoWorking on a large scale & fluid Node project at the moment and we probably see at least a dozen dependency updates a week. Never caused a problem. The community as a whole is pretty strict in it's respect for versioning conventions.
- ilaksh 13y agoWell, I had an issue with Express going up a major version also to 3.0 but it was actually my fault because I didn't specify the major version in my package.json, i.e. 2.x. If I had done that the breaking changes would not have got me.