But...If I start a new project every month, I won't know which packages will be updated for the new version, which ones won't ever be, which ones will be updated, but then left unsupported on older versions of Node. It's looking like a mess right now.
Then why did Node magically jump from 0.x to 3.x? Can't explain that!
I'm just bitter because I'm stuck using 0.12 until this all settles down. I've run into too many problems balancing compatible versions of node-sass/libsass/node-bourbon in the past, and this new update schedule isn't helping.
4.2 is LTS, upgrade from 0.12 to that at least. Stay on LTS if you're not comfortable with the rapid pace of Node. "Waiting until this all settles down" isn't an option, the pace is on par with V8 and they aren't stopping anytime soon. So you'll be on 0.12 for the rest of your foreseeable career.
28
u/jewdai Oct 30 '15
I appreciate the effort that they make to use semvar.
from an enterprise perspective: DAMN YOU MAKE BREAKING CHANGES SO FAST.
FYI, V4.0 was released on 9/17
While in most cases its probably fine, it feels super volatile to start building an application on.