> > Some quick factoids: > The Dart team built the V8 engine, which compiles to machine code from what I have read, but there is a hidden (lightweight?) VM in there. The code base is similar enough that advancements in Node 0.12 is for me moving quickly to Dart. The important point for me is that we *do* want Node to support clients with global JS optimization. It does tree pruning, which means Node will analyze client apps and drop all of the unused code from libraries. So Node handing compiled/linked/optimized/secured JS client programs is desirable -- no module loading on client??! That is a great service Node can perform and it can do this almost with browserify. Browserify is important but a Google sponsored JS optimization tree prune is significant. But it is open source and if browserify can deliver than all of the other Dart things in all likelihood will be in Node.
-- -- 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 [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
