> If I would choose which tool is best for my project just by popularity factor > I wouldn't go far.
I have a way to solve this issue that emulates pattern matching in javascript `github/dscape/p` while maintaing valid JS semantics. Its sooooo unpopular even I dont use it :) (but it works.... I think!) Still i think pattern matching is the best thing since sliced break. But will it be the way people write programs in node? (Unfortunately) No. In a more serious tone, this is about our module ecosystem and node core. We settled on streams and callbacks. We have tried promises plus a million other crazy things but as in everything in callbacks and streams were the choice of the community. @mikeal's point was about that, everyone uses async in their modules in npm showing what our ecosystem adopted. Is it not evident that these choices are hugely correlated to the success of npm and why its so easy to use modules? You can do other choices but will people the use your modules? Will this trend change in the future? Probably not. Nuno -- 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
