31–40 of 132 posts
I found this out last night at 3am after rushing to provision a server. i don't have a great handle on semver or dev cycles, point ceded, but they released 4.2 on october 12th. thats like .1 every 2 days.
Earlier quoted context omitted.
JS in general moves fast and packages range from great to WTF in quality. I would suggest using Babel(or something similar) for all future JS development. That way you can use ES2015/2016 features now and have them work in most environments. I have a built a small API using express and passport and so far these node changes have not impacted my code. Another option for fast API development is Java 8 with SpringBoot a…
But then you have to keep up with Babel changes too... http://babeljs.io/blog/2015/10/29/6.0.0/
I recently looked at using Node for a simple API backend. ES6 seems like it's not there yet, the stability of Node makes me wary. Constant changes seem exhausting to keep up with. For a simple microservice api you don't want to be upgrading it every 3 days. The continuous change doesn't make sense to me. Trying to get up to speed on all the Node.js ecosystem feels exhausting, only to have it change a few weeks later.…
Yap good choice. Python to me is more readable (so I can understand my own code and others' better) and I find the echo system to be friendlier and more mature.
Uhh, wait, wasn't nodejs 4.0 only like a month ago? So are there going to be breaking changes every few months now?
Yeah, why not? Just because they upgrade node, doesn't mean you have to use that version. If you want a stable version, you'll be on the LTS release that will be supported for a long while
1. There is no one forcing you to upgrade, 4.2 is LTS, you've got 2yrs+
2. 5.0 followed 4.0 so closely because 4.0 was the iojs/node merge and 5.0 was to correspond with the new V8 release, future major bumps will be closer to 6mo (to match V8)
If you're looking for solid, long term stability, you are perfectly fine sticking with v4.0.0, as its marked an "LTS" release. This means it'll be actively receiving minor- and patch-level updates for 18 months, then for 12 months thereafter it'll get updates for severe bugs and security problems (what they call "maintenance" mode) [2].
[1] https://twitter.com/rvagg/status/659871982670884864 [2] https://medium.com/@nodesource/essential-steps-long-term-sup...
I found this out last night at 3am after rushing to provision a server. i don't have a great handle on semver or dev cycles, point ceded, but they released 4.2 on october 12th. thats like .1 every 2 days.
Even non-semver version numbers are rarely decimal numbers, even though the major/minor distinction may be less clearly defined.
So talking about a 0.1 every n days inferred from the date of a 5.0 vs. A 4.2 release doesn't make any sense; if there were actual minor releases that frequently, it would, but that is a different thing.
Earlier quoted context omitted.
Yes, I'm very excited about the spread operator! I've been spoiled by Firefox.
Looking at documentation.. does this only work on lists (or list like object)? I.e. you can't "expand" a k:w object? Or is there another operator for this? Example: function foo(a=1, b=2, c=3) { return a * b * c;} dict = {'b': 4, 'c': 6}; foo(...dict);
You can still do something like:
foo(... Object.keys(dict).map(name => dict[name]))
However, the spread operator doesn't match the argument names to the object names. So the above call would mean the following:
foo(4, 6)
foo(undefined, 4, 6)
let x = { a : 1, b : 2, c : 3 };
let { a, ... rest } = x;
console.log( ... rest ); // { b : 2, c : 3 }Earlier quoted context omitted.
Yes, I'm very excited about the spread operator! I've been spoiled by Firefox.
Looking at documentation.. does this only work on lists (or list like object)? I.e. you can't "expand" a k:w object? Or is there another operator for this? Example: function foo(a=1, b=2, c=3) { return a * b * c;} dict = {'b': 4, 'c': 6}; foo(...dict);
[1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... [2] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
Earlier quoted context omitted.
But then you have to keep up with Babel changes too... http://babeljs.io/blog/2015/10/29/6.0.0/
Why this urge to keep up to the latest and greatest? Especially for a transpiler? If it is converting your code just fine, why update?