4 ms·

One of the performance improvements [0] is pretty crazy! Up to an 18,000% performance increase. [0] https://github.com/nodejs/node/pull/5123 https://github.com

One of the performance improvements [0] is pretty crazy! Up to an 18,000% performance increase. [0] https://github.com/nodejs/node/pull/5123 https://github.com/nodejs/node/pull/5123

btd 11y ago
Yes, but it breaks some cases. I'd recommend to wait 5.7.1 (https://github.com/nodejs/node/issues/5400 https://github.com/nodejs/node/issues/5400)
- amelius 11y ago
  Probably an ignorant question but this makes me wonder: how can they release when their tests don't pass?
  - johnchristopher 11y ago
    Break early, break often :-).
  - k__ 11y ago
    Maybe psychology... People won't use x.y.0 so they build in a bug to push to x.y.1 afterwards
  - mc808 11y ago
    I haven't been following, but it looks like the tests were passing and they just didn't have tests to prevent these issues that came up.
- samcheng 11y ago
  This is exactly why I've stayed away from this stack wherever possible!
  - jzwinck 11y ago
    I hope you stay away from GCC as well, which for example broke C++ in 4.7.0 and fixed it in 4.7.2. Any new major release is bound to break something for someone. Prudence suggests adopting a major release only after a few months. This applies to all platforms.
    - loevborg 11y ago
      This is not true. Some platforms, such as Clojure, are usually very stable once released, and there is rarely the need for point releases, as the code was stabilized during the alpha/rc periods.
    - samcheng 11y ago
      You're right; I was a bit harsh. I'm just really conservative platform-wise - Node is just starting to get there. The Node/npm ecosystem does still feel a bit wobbly as an application platform, though, kind of like Ruby was five years ago...
kenOfYugen 11y ago
Great news! Node.js could greatly benefit from more reimplementations of its native modules. I had implemented the `fs.readdir` module in C and saw some good performance gains (it was a hackish experiment I did some time ago and can't remember numbers). The `http` module is said to be outperformed by `eshttp` [1] by a factor of 2 times, which is written in pure JavaScript. There is also `node-lwan` [2], an experiment in using `lwan` [3] in place of the built in `http` module. Since its the most performant web server in JSON serialization, according to techempower.com benchmarks [4], performance gains are to be expected. [1] https://github.com/iefserge/eshttp https://github.com/iefserge/eshttp [2] https://github.com/raadad/node-lwan https://github.com/raadad/node-lwan [3] http://lwan.ws/ http://lwan.ws/ [4] https://www.techempower.com/benchmarks/#section=data-r12&hw=peak&test=json https://www.techempower.com/benchmarks/#section=data-r12&hw=...

One of the performance improvements [0] is pretty crazy! Up to an 18,000% performance increase. [0] https://github.com/nodejs/node/pull/5123 https://github.com/nodejs/node/pull/5123

btd 11y ago

Yes, but it breaks some cases. I'd recommend to wait 5.7.1 (https://github.com/nodejs/node/issues/5400 https://github.com/nodejs/node/issues/5400)

amelius 11y ago
Probably an ignorant question but this makes me wonder: how can they release when their tests don't pass?
- johnchristopher 11y ago
  Break early, break often :-).
- k__ 11y ago
  Maybe psychology... People won't use x.y.0 so they build in a bug to push to x.y.1 afterwards
- mc808 11y ago
  I haven't been following, but it looks like the tests were passing and they just didn't have tests to prevent these issues that came up.
samcheng 11y ago
This is exactly why I've stayed away from this stack wherever possible!
- jzwinck 11y ago
  I hope you stay away from GCC as well, which for example broke C++ in 4.7.0 and fixed it in 4.7.2. Any new major release is bound to break something for someone. Prudence suggests adopting a major release only after a few months. This applies to all platforms.
  - loevborg 11y ago
    This is not true. Some platforms, such as Clojure, are usually very stable once released, and there is rarely the need for point releases, as the code was stabilized during the alpha/rc periods.
  - samcheng 11y ago
    You're right; I was a bit harsh. I'm just really conservative platform-wise - Node is just starting to get there. The Node/npm ecosystem does still feel a bit wobbly as an application platform, though, kind of like Ruby was five years ago...

kenOfYugen 11y ago

Great news! Node.js could greatly benefit from more reimplementations of its native modules. I had implemented the `fs.readdir` module in C and saw some good performance gains (it was a hackish experiment I did some time ago and can't remember numbers). The `http` module is said to be outperformed by `eshttp` [1] by a factor of 2 times, which is written in pure JavaScript. There is also `node-lwan` [2], an experiment in using `lwan` [3] in place of the built in `http` module. Since its the most performant web server in JSON serialization, according to techempower.com benchmarks [4], performance gains are to be expected. [1] https://github.com/iefserge/eshttp https://github.com/iefserge/eshttp [2] https://github.com/raadad/node-lwan https://github.com/raadad/node-lwan [3] http://lwan.ws/ http://lwan.ws/ [4] https://www.techempower.com/benchmarks/#section=data-r12&hw=peak&test=json https://www.techempower.com/benchmarks/#section=data-r12&hw=...