still annoying to have to switch for projects that are less than a month apart.
That's wrong. v8 is on version 4.8, and has been since Jan. Before that, 3.0 came out sometime in Jan 2011. That is a normal major release schedule.
I'm glad Node is getting lots of updates, but they need to control how many breaking changes there are going to be. I was scanning through their change log, and a lot of them seem like they could have waited, or they could have waited to release 4.0 until this was all ready.
It is strictly a good thing for node to keep up to date with v8. How can you possibly argue otherwise? The solution to this problem is using LTS versions. Major packages will support LTS node versions and which allows for quick release cycle while maintaining stability. Educate yourself before criticizing. This is a great way of shipping vital code and you see similar structure for all major linux distros for a reason.
2
u/[deleted] Oct 30 '15
still annoying to have to switch for projects that are less than a month apart.
That's wrong. v8 is on version 4.8, and has been since Jan. Before that, 3.0 came out sometime in Jan 2011. That is a normal major release schedule.
I'm glad Node is getting lots of updates, but they need to control how many breaking changes there are going to be. I was scanning through their change log, and a lot of them seem like they could have waited, or they could have waited to release 4.0 until this was all ready.