Node.js v4 Release Timeline • Hacker News Board

Re: Node.js v4 Release Timeline

#11

Post by jestar_jokin » Fri, Sep 04, 2015, 12:09 AM UTC

netcraft wrote: post #7

So excited this is finally happening. I enjoy every bit of node I get to write, really excited for the updated features. Babel has taken a lot of the edge off, but I dont want to pull babel in for every script.

I'm curious, what is your development background, and what do you enjoy most about Node.js?

I come from a Java background, but have been working exclusively with Node.js for the last eight months. Everything I write, I can't help thinking things like "this problem has already been solved in Java many times over", and "this would be safer in a statically typed language", and "this would be faster to write in anything else" (though this is more a reflection on my choice of libs).

Re: Node.js v4 Release Timeline

#12

Post by [deleted] » Fri, Sep 04, 2015, 12:11 AM UTC

[deleted]

Re: Node.js v4 Release Timeline

#13

Post by timdorr » Fri, Sep 04, 2015, 12:17 AM UTC

One issue to go: https://github.com/nodejs/node/issues/2516

A .bat file is holding up the whole thing!

Re: Node.js v4 Release Timeline

#14

Post by seiji » Fri, Sep 04, 2015, 12:23 AM UTC

rakk wrote: post #8

Most excited about v8 4.5. Native support for arrow functions and stuff like Array.from really makes the dev experience feel so much smoother.

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.

Re: Node.js v4 Release Timeline

#15

Post by [deleted] » Fri, Sep 04, 2015, 12:25 AM UTC

seiji wrote: post #14

rakk wrote: post #8

Most excited about v8 4.5. Native support for arrow functions and stuff like Array.from really makes the dev experience feel so much smoother.

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.

[deleted]

Re: Node.js v4 Release Timeline

#16

Post by netcraft » Fri, Sep 04, 2015, 12:26 AM UTC

jestar_jokin wrote: post #11

netcraft wrote: post #7

So excited this is finally happening. I enjoy every bit of node I get to write, really excited for the updated features. Babel has taken a lot of the edge off, but I dont want to pull babel in for every script.

I'm curious, what is your development background, and what do you enjoy most about Node.js? I come from a Java background, but have been working exclusively with Node.js for the last eight months. Everything I write, I can't help thinking things like "this problem has already been solved in Java many times over", and "this would be safer in a statically typed language", and "this would be faster to write in anything…

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 what I need to this is what I have down considerably.

Re: Node.js v4 Release Timeline

#17

Post by sciolistse » Fri, Sep 04, 2015, 12:44 AM UTC

seiji wrote: post #14

rakk wrote: post #8

Most excited about v8 4.5. Native support for arrow functions and stuff like Array.from really makes the dev experience feel so much smoother.

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.

It's been "the same javascript everywhere" mostly due to the ECMAScript group kinda stalling for the past 15 years. The stabilisation created through that has been useful, but the plan is to transition the spec onto a one-year update cycle.

That means that going forward we'll likely have more feature mismatch between engines, making backward compatibility compilers pretty important.

I'm not entirely sure if that's good or not.

Re: Node.js v4 Release Timeline

#18

Post by potatosareok » Fri, Sep 04, 2015, 1:02 AM UTC

netcraft wrote: post #7

So excited this is finally happening. I enjoy every bit of node I get to write, really excited for the updated features. Babel has taken a lot of the edge off, but I dont want to pull babel in for every script.

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.

Re: Node.js v4 Release Timeline

#19

Post by rakk » Fri, Sep 04, 2015, 1:15 AM UTC

seiji wrote: post #14

rakk wrote: post #8

Most excited about v8 4.5. Native support for arrow functions and stuff like Array.from really makes the dev experience feel so much smoother.

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.

Chrome (logically) already supports features of the new JS spec that 'only now' get put into node. With automatic updates for browser being the trend currently I also think that it is now easier to keep the server and browser support for JS in sync.

Re: Node.js v4 Release Timeline

#20

Post by mattkrea » Fri, Sep 04, 2015, 1:56 AM UTC

rakk wrote: post #19

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.

Chrome (logically) already supports features of the new JS spec that 'only now' get put into node. With automatic updates for browser being the trend currently I also think that it is now easier to keep the server and browser support for JS in sync.

Not necessarily. I don't think the v8 team really consider the Node project so breaking changes in v8 take some time to get merged into Node/io.js. This is the reason that arrow functions are only shipping now when v8 marked them complete a while back. AFAIK Node is somewhere around 3+ months behind Chrome.