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/
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.
HANK 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.
One thing that's certain - Node 0.12 will be released sometime later this
year.
Out of curiosity, any updates on this?
He probably meant the fiscal year. :-)
I guess a certain kind of pronouns really slowed it all down :P
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.
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!
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/
* 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.
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.
Is there any update on this? Latest breaking news? General feeling? Rough timescale?
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.
Thanks! I am looking forward to yield becoming mainstream. One "little" thing and so much code becomes trivial.
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.
댓글 없음:
댓글 쓰기