On Saturday, April 14, 2012 8:35:09 PM UTC-4, r...@tinyclouds.org wrote: > > > This is a discussion to bring up with the EcmaScript committee. >
Or Node could lead the way by example, just like browsers do before creating a spec and advocating for it with the W3C. Committees don't feel the pain that us soldiers in the trenches do, and when all you have is an "idea" it's so easy to get shot down. Innovation by committee is hard. Browsers have learned that precedents tested in the trenches are far more powerful. As a pertinent example, take CoffeeScript. It has already been quoted extensively by ES committee members, and is influencing its new directions. See e.g. http://brendaneich.com/tag/javascript-ecmascript-harmony-coffeescript/ The callback hell is clearly a major nuisance in JavaScript (c.f. how long this thread is, and possibly the largest pull request discussion on Github: https://github.com/jashkenas/coffee-script/pull/1942). It gets particularly annoying when one tries to do any type of data aggregation from multiple sources (databases, SaaS APIs, etc) or sysops scripts (run this command, then that, etc). Since these are common use cases for server-side scripts, Node is at a unique position to lead by example and make a proposal. And frankly I'd prefer if the proposal came from Node's core team (who have a proven track record to design elegant and simple interfaces) than a group of academics. That's just my $0.10 though... -- Artur Adib Mozilla Labs http://twitter.com/arturadib -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
