V8 的最终版本为 3.28.73 从 0.10 (Mar 11, 2013) 发布到现在已经差不多两年的时间了, 真是哪吒一样难产呀 一年一度的 nodesummit (2.10-11)又要召开了, 不知道会否有重大消息或进展 以下为 0.12 的一些主要改动:

• Streams 3 The Streams implementation now works the way you thought it already should, without introducing any changes to the API. Basically this means no more getting stuck in “old mode”, there are only streams that are flowing or not. Streams now support the use of cork and uncork mechanisms to prevent flushing writes out to the system if an application is going to be performing many writes in a row. There is an implicit uncork performed when you end a writable stream.
• HTTP maxSockets are no longer limited to 5. The default is now set to Infinity with the developer and the operating system given control over how many simultaneous connections an application can keep open to a given host. Proper KeepAlive support means that sockets will stay open until they timeout at the configured time, are closed by the remote side, or the process exits. Developer’s no longer have to make sure requests have been pipelined to keep the socket open, or use an alternative module to get that support. Developers can also now explicitly flushHeaders to ensure time to first byte is low and proxied connections are held open.
• Cluster Now has two modes of operation, the new default is a round robin distribution mechanism where the master accepts new connections and distributes them to your workers. If you want you can still opt back into the old method where your workers are responsible for acception connections.
• TLS We have the new TLSWrap mechanism under the hood, this eliminates quite a few of the hops back and forth between JavaScript and our C++ implementations. Added APIs for asynchronous SNI callbacks, OCSP stapling, and storage events.
• Buffer We use a more accurate mechanism for allocating memory for buffers now, which means you’ll see less overhead and impact from holding onto to small slices of Buffers. This reduces the amount of memory pressure on the system, which means GC runs are quicker, which means Node.js is on CPU less, and thus lower latency for your applications.
• child_process spawnSync/execSync have been added to facilitate synchronous child processes, warning your node process won’t make forward progress while waiting for the child to exit, caveat emptor!
• Crypto Added APIs for loading custom engines for use with compiled in OpenSSL. More APIs support supplying the pass phrases. Added APIs for RSA public/private key encryption/decryption.
• VM The module is now based on the Contextify module, which shares values from the sandbox to avoid missing changes inside the execution from appearing in the parent context.
• Initial support for ECMAScript Internationalization API 1.0 (ECMA-402) By default, Node.js v0.12.0 binaries are shipped with ECMA-402 support, but only for the English language. In other words, the ECMA-402 API is working as you would expect, but only data for the English language is included. You can find more info on how to include more languages in the Wiki.

详细信息请参看官方博客