Node.js V0.12 release

[elad dare]

Hi All,

I'm a new Node fan, moving from classic java...

I have seen a few remarks from node developers on V0.12 with expected performance enhancements.

My question : does anyone know when should this release is due ?
I'm very much into performance and last benchmarks on http://www.techempower.com/benchmarks/ make me wonder what will be the improvement in the next release...

Thanks,
Elad.

[Андрей Листочкин]

Hi, Elad.

1. Node 0.12 release date.

There's no fixed release date, just like it never was with any Node
version. It's done when it's done. I.e. when all planned features are
implemented and all performance regressions are addressed. Among the three
of the following:
- features
- performance
- release schedule
Node team consistently picks the first two, and it's the release schedule
that suffers. Node community agrees that it's the right strategy for a
project since the final releases are very stable and their behavior in
production environments is very predictable.

One thing that's certain - Node 0.12 will be released sometime later this
year. Isaac knows better, but given the track record of older releases
(0.8 and 0.10) I would say that November is a very realistic target.
Probably earlier, but who knows? So far there were 2 very early releases
of Node 0.11 without any significant changes shipped yet. So, Node team
will need time for development and stabilizing Node 0.11 first before
switching to 0.12.

2. Performance improvements.

Node is a mature project with most easy performance opportunities already
explored, and it's not going to magically become twice as fast. 2-5%
overall speedup with 2x speedups or 10% slowdowns in some particular
scenarios is something that you can safely expect. It means that on
TechEmpower benchmarks Node won't move significantly up or down due to a
new version release.

If this level of performance is not enough for your task, pick another
technology. Just make sure that you use a set of benchmarks that represent
your task closely enough. Most benchmarks don't since they are too generic
and too narrow in scope. Node is optimized for IO-bound tasks. If your
application spends most of the time talking to disk or to network Node
should work perfectly fine for you.

Andrey

Node 0.12 is a stabilized version of Node 0.11 which is currently in
works. There


On Thu, 20 Jun 2013 00:40:57 +0300, elad dare <eladda...@gmail.com>
wrote:

> Hi All,
>
> I'm a new Node fan, moving from classic java...
>
> I have seen a few remarks from node developers on V0.12 with expected
> performance enhancements.
>

> My question : does anyone know when should this release is due ?I'm very

> much into performance and last benchmarks on
> http://www.techempower.com/benchmarks/ make me wonder what will be the
> >improvement in the next release...
>
> Thanks,
> Elad.
>
>
>
>
>
>
>

> --
> --
> Job Board: http://jobs.nodejs.org/
>
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>
> You received this message because you are subscribed to the Google
>
> Groups "nodejs" group.
>
> To post to this group, send email to nod...@googlegroups.com
>
> To unsubscribe from this group, send email to
>
> nodejs+un...@googlegroups.com
>
> For more options, visit this group at
>
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
>
> ---
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
>
> To unsubscribe from this group and stop receiving emails from it, send
> an email to nodejs+un...@googlegroups.com.
>
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



--
Using Opera's mail client: http://www.opera.com/mail/

[elad dare]

Hello Andrey,

THANK you very much for the detailed answer.
Regarding your comment on performance, I understand it completely... choosing node has upside and downside, just as with any other technology.

Thanks,
Elad.

[Ryan Zec]

On Thursday, June 20, 2013 3:24:46 AM UTC-4, Андрей Листочкин wrote:

One thing that's certain - Node 0.12 will be released sometime later this  
year.

Out of curiosity, any updates on this?

[Mark Hahn]

He probably meant the fiscal year.  :-)

--

[Alex Kocharin]

О©╫

09.01.2014, 21:46, "Ryan Zec" <bas...@gmail.com>:

On Thursday, June 20, 2013 3:24:46 AM UTC-4, О©╫О©╫О©╫О©╫О©╫О©╫ О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫ wrote:

One thing that's certain - Node 0.12 will be released sometime later this О©╫
year.

О©╫

Out of curiosity, any updates on this?

О©╫

I guess a certain kind of pronouns really slowed it all down :P

О©╫

[Forrest L Norvell]

There are a number of loose ends that the core team is nailing down right now and a couple features that are in the final stages of being stabilized, but at this point, I think the core team's goal is to get 0.12 out as soon as possible. There are no major showstoppers that I know of. I would be very surprised if 0.12 weren't out by the end of February (at the very latest).

Note: I'm not a member of core, just an interested bystander.

Forrest

On Thu, Jan 9, 2014 at 9:45 AM, Ryan Zec <bas...@gmail.com> wrote:

--

[Alex Fernandez]

Hi all,

El viernes, 10 de enero de 2014 03:09:36 UTC+1, Forrest L Norvell escribió:

There are a number of loose ends that the core team is nailing down right now and a couple features that are in the final stages of being stabilized, but at this point, I think the core team's goal is to get 0.12 out as soon as possible. There are no major showstoppers that I know of. I would be very surprised if 0.12 weren't out by the end of February (at the very latest).

This page is the first hit for "node v0.12 release", any updates on when to expect node v0.12? I am quite excited about it!

Alex.

[Forrest L Norvell]

This is what I get for confidently stating a ship date... Node 0.12 is pretty close to release right now, but I've heard there will be another version of Node 0.11 before the 0.12 release, and I imagine with TJ doing the Node Roadshow right now (http://www.joyent.com/noderoad/about), it will take a little bit longer. The most recent things to land that have affected the release:

* upgrading to V8 3.24.35

* finalizing what interface will be exported from the new tracing module

* getting Node in sync with libuv 0.12

Beyond that, there's the usual end-of-dev-cycle bug fixing. As far as I know (NOTE: I'm not a member of the core team, but I did discuss this with TJ in some detail last week) there are no features and no large blockers pending. It's just a matter of getting everybody's ducks in a row. That said, I think the best thing to say right now is that it'll release when it's ready, and it's pretty close to being ready.

F

[Alejandro Fernandez]

2014-03-21 1:46 GMT+01:00 Forrest L Norvell <for...@newrelic.com>:

Beyond that, there's the usual end-of-dev-cycle bug fixing. As far as I know (NOTE: I'm not a member of the core team, but I did discuss this with TJ in some detail last week) there are no features and no large blockers pending. It's just a matter of getting everybody's ducks in a row. That said, I think the best thing to say right now is that it'll release when it's ready, and it's pretty close to being ready.

Thanks for the update! I see that you are being prudent and have avoided advancing any concrete date this time... Let us hope it is soon anyway.

Alex.

[M Murphy]

Hello,

Is there any update on this?  Latest breaking news?  General feeling?  Rough timescale?

Many thanks, Max

[Forrest Norvell]

On Wed, May 28, 2014 at 9:38 AM, M Murphy <maximilli...@gmail.com> wrote:

Hello,

Is there any update on this?  Latest breaking news?  General feeling?  Rough timescale?

Two weeks. Or at least that's been my answer since mid-February. There's one more 0.11.x dev release in the pipeline to test a lot of little bug fixes that have been added since 0.11.13, and the last I heard, the plan was to basically treat that release as a 0.12 release candidate. The project has been unusually quiet about their plans lately, though, so this is just what I heard the last time I was talking.

It's definitely been a while since a release, and the 0.12 release process is well into extra innings. If you're annoyed or frustrated by this, take comfort from knowing you're not alone.

F

[M Murphy]

Thanks!  I am looking forward to yield becoming mainstream.  One "little" thing and so much code becomes trivial.

--
Job board: http://jobs.nodejs.org/
New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to a topic in the Google Groups "nodejs" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/nodejs/Gj08gMftxi4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to nodejs+un...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CAHG3qKp3jMurwZs%2Bd3GS0K7gzBDW6EMn1rXEcMPJLnM5xjgjyA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Forrest Norvell]

On Mon, Jun 2, 2014 at 11:46 AM, M Murphy <maximilli...@gmail.com> wrote:

Thanks!  I am looking forward to yield becoming mainstream.  One "little" thing and so much code becomes trivial.

Just be aware that function * and yield will still be behind the --harmony flag for now, and that generators are still due for a few bug fixes in the specification before the end of the year. So even once 0.12 is released, people should use generators with care.

F

​

[M Murphy]

OK, I'll hold on.  Anything to move people on from promises when they try to escape "callback hell".  Promises are a sort of mid point between generators and event emitters and I don't see that they actually deliver on their promise of being a worthwhile compromise.  Heavyweight, slow code, even with bluebird.  Still, we will see!

--

Job board: http://jobs.nodejs.org/
New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to a topic in the Google Groups "nodejs" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/nodejs/Gj08gMftxi4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to nodejs+un...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CAHG3qKoqdaDjRkvxkZXoBk0-mgSy93Sjq4Pdw2cswd%2B9MBTraA%40mail.gmail.com.

[Petka Antonov]

If you really believe that, can you make an issue on the github issue tracker of bluebird?

If the code you produce is heavyweight and slow compared to equal code using some other abstraction, and you believe you are truly utilizing bluebird to fullest, that's a bug you should report.

[Sarang Sapre]

Is there any speculations when Node v0.12 is going to be available? 

I'm building some piece of software using nodeJS v0.10.x - Wanted to move to NodeJS v0.11.x - But not sure if I should because it is marked as unstable. And its not clear as to which things are stable vs unstable 

e.g. npm install behind firewall fails in v0.11 is important for me. 

Thanks and Best Regards,

Sarang Sapre

[Kp]

Hi,

I would also like to know some update on this. I'm very interested in new JS features like generators and also updated V8 as I noticed that there are changes that break C++ addons.

Cheers,

Petr

[Timothy Quinn]

[update] Node advisory board post from 2014-11-07 notes that "0.12 is done except for a patch on windows".

Maybe we will be getting a nice present for this Christmas!

(ps Can't wait for production ready execSync() so I can start porting many of my server side and desktop tools to Node.

[Imre Fazekas]

Christmas? I certainly hope not! :)

Was waiting for the meeting minutes of the 17th of this month but nothing so far...

Could anyone share some news or even better a date?

Thanks!

[Kevin Ludwig]

I guess estimation is hard. Perhaps a more agile approach is required.

[Issac Roth]

FWIW:

https://twitter.com/nodejs/status/545349270241435648

You received this message because you are subscribed to the Google Groups "nodejs" group.

To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.

To post to this group, send email to nod...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/a387b07d-e65f-4f19-8fef-198e90025727%40googlegroups.com.

[Egor Egorov]

This is exactly why io.js happened. 

[Ryan Zec]

Which is exactly why I am not thinking about looking into Go for my backend needs

To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/45ce98c4-66ef-4a4d-9866-4e58b59c660b%40googlegroups.com.

[Timothy Quinn]

Update from another thread: 

Currently, the only outstanding issue I'm aware of is the merge of v0.10 to v0.12:https://github.com/joyent/node/pull/8886. We're doing our best to get that done and move forward with the 0.11.15 release.

[Timothy Quinn]

Wohoo. Node.js branch 0.11.15 was created yesterday on Github.

As long as there are no big regressions, Node.js v0.12 should be just weeks away.