hehe. One thing I minunderstood is that there is a difference between Dart competing with Coffee and Browserify and Dart competing with Node. Dart as a task within a Gruntfile doing what coffee and browserify does is certainly a good idea. At the same time I have not been able to buy into coffee, but I would if I could do it. I am paying dues. But if people are able to buy into Dart using Node on the server side, then yeah I would do that. it is a lovely language.
On Wednesday, March 5, 2014 11:56:31 AM UTC-8, ajlopez wrote: > > Node has nothing to do with clients. It was born without hard links to > client. > > And it was a good decision. It's not only "client" as a browser. It's > about "client (browser/native/internet of things)" and "other servers > (maybe other nodes)". Node has a great focused mission: to be the bricks of > the first SkyNet ;-) > > The other side (call it "client"?) is under vibrant development. Linking > Node to "the other side" is not the way to follow. > > Vive le difference! > > Angel "Java" Lopez > @ajlopez > > > On Wed, Mar 5, 2014 at 4:49 PM, Pat Monardo <[email protected]<javascript:> > > wrote: > >> 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]<javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> 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] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- -- 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.
