Node.js v4 Release Timeline • Hacker News Board

Re: Node.js v4 Release Timeline

#31

Post by Killswitch » Fri, Sep 04, 2015, 4:49 AM UTC

findjashua wrote: post #23

seiji wrote: post #14

Earlier quoted context omitted.

I may be out of the loop here, but wasn't the big benefit of JavaScript everywhere that it's the same JavaScript everywhere? Does it matter if server-side is JavaScript Next Gen and browsers lag by a few years of features? Too many more iterations of this and you'll be back to two programming languages again and web developers heads will explode from having to learn two things instead of one things.

with babel you can use the latest js everywhere.

Latest JavaScript that can be transpiled to ES5 anyway.

Re: Node.js v4 Release Timeline

#32

Post by Killswitch » Fri, Sep 04, 2015, 4:50 AM UTC

abritinthebay wrote: post #24

potatosareok wrote: post #18

Earlier quoted context omitted.

Am I doing something wrong? I find NPM very slow and buggy compared to maven which just works for me. It could be that I'm on Windows or just more familiar with Maven. Use an internal nexus for both proxying NPM and maven.

> It could be that I'm on Windows It is. NPM is a joy to use on Mac or Unix.

And thankfully Microsoft is helping mitigate this issue.

Re: Node.js v4 Release Timeline

#33

Post by deathtopg » Fri, Sep 04, 2015, 6:54 AM UTC

so does this mean I don't update iojs and start updating node.js?

Re: Node.js v4 Release Timeline

#34

Post by te_chris » Fri, Sep 04, 2015, 6:55 AM UTC

dmarg wrote: post #27

netcraft wrote: post #16

Earlier quoted context omitted.

Mostly dynamic languages. I really like statically typed languages for certain tasks, but many times a dynamic language that gets out of your way can be quite liberating. It takes a lot of trust compared to a language where your compiler is what you trust - and occasionally you spend a bit of extra time tracking down why things are in a state other than what you expect, but on the whole it takes the time from this is…

Yes, statically typed languages can help. However, if you have good test coverage then you can test for that stuff and get a similar experience. For example, if a test break then you know your variable is not a number anymore when you need it to be.

Manually writing tests for things which the compiler automatically picks up is not my idea of 'a similar experience'. Background: ruby and is dev who is now learning Scala and loving having type safety

Re: Node.js v4 Release Timeline

#35

Post by k__ » Fri, Sep 04, 2015, 7:56 AM UTC

Killswitch wrote: post #30

paperwork wrote: post #29

Earlier quoted context omitted.

Doesn't this include the new class syntax? If so, will the standard libraries change as well to use the new classes?

Yes, classes are stable in V8 4.5 so Node.js 4.0 will have classes without runtime flags.

Is there a list with all the supported ES2015 features?

Re: Node.js v4 Release Timeline

#36

Post by Arnavion » Fri, Sep 04, 2015, 8:12 AM UTC

mattkrea wrote: post #26

ofrobots wrote: post #25

Earlier quoted context omitted.

This is not really accurate. Arrow functions shipped in Chrome on Tuesday (Sep 1) with Chrome 45 (V8 4.5).

Gotcha. I guess marking them "shipped" just puts them into canary? That was done a while back. https://code.google.com/p/v8/issues/detail?id=2700

V8 has had arrow functions for a long time, but until recently they were not fully spec compliant. That is also why iojs put them behind a flag (separate from the flag that enabled stable harmony features).

Re: Node.js v4 Release Timeline

#37

Post by pluma » Fri, Sep 04, 2015, 8:17 AM UTC

Killswitch wrote: post #31

findjashua wrote: post #23

Earlier quoted context omitted.

with babel you can use the latest js everywhere.

Latest JavaScript that can be transpiled to ES5 anyway.

Except for symbols and Object.observe.

Well, you can emulate those in ES5 but it's just not the same.

Re: Node.js v4 Release Timeline

#38

Post by Arnavion » Fri, Sep 04, 2015, 8:49 AM UTC

If you're hoping to use native V8 Promises, beware using them with other promise libraries / custom thenables because of https://code.google.com/p/v8/issues/detail?id=4162 (more detail and test case in https://github.com/zloirock/core-js/issues/78 )

Re: Node.js v4 Release Timeline

#39

Post by egeozcan » Fri, Sep 04, 2015, 9:33 AM UTC

k__ wrote: post #35

Killswitch wrote: post #30

Earlier quoted context omitted.

Yes, classes are stable in V8 4.5 so Node.js 4.0 will have classes without runtime flags.

Is there a list with all the supported ES2015 features?

Probably the same as io.js[0].

[0]: https://iojs.org/en/es6.html

Re: Node.js v4 Release Timeline

#40

Post by stephenr » Fri, Sep 04, 2015, 9:44 AM UTC

So it seems this is v4 because io.js got to v3 in it's short lifetime.

Is Chrome somehow setting the pace for version numbers? We don't have major.minor.path. Semver is pointless.

A version is an integer, and every change is a new version?

How long until we see Uint32 overflows on a version number?