The Node.js community blog on Medium, with posts on the io.js and Node.js split, governance, and WebSocket implementations.
HN links it for the io.js and Node.js reconciliation story, including the foundation proposal and a post on fragmentation; commenters mainly cite it as background.
Number of connections, message size, and frequency of messages sent are three main parameters to measure performance, and for some frameworks like Engine.IO, number of connections seems to have the biggest impact on performance (https://medium.com/node-js-javascript/b63bfca0539). It would be good to see the benchmarks with much higher number of connections, as non-blocking IO is usually why people choose Node.js platform.
@Mikeal has a couple of posts on the subject:
- https://medium.com/@mikeal/on-corporate-ownership-of-open-source-786ebd15847e
- https://medium.com/node-js-javascript/fragmentation-7e87d28f60fe
more information here: https://medium.com/node-js-javascript/io-js-week-of-february-17th-9422a589302a
armv8 / aarch64 is interesting on the (low power) server side.
Reminds me of this: https://medium.com/node-js-javascript/growing-up-27d6cc8b7c53