> The idea is to have a curated list of modules with appropriate stability and support guarantees. If you find a bug, we'll make sure it gets fixed in a timely manner; you won't be at the mercy of the module author.
A priviliged list of approved modules is dangerous. It stales development. Instead fix the npm discoverability problem to make it trivial to search for a list that meets the criterias. The discoverability problem is a lot harder but far more worthwhile and it will solve that very problem. On Sat, Dec 15, 2012 at 11:30 AM, Ben Noordhuis <i...@bnoordhuis.nl> wrote: > On Sat, Dec 15, 2012 at 7:52 PM, Mark Hahn <m...@hahnca.com> wrote: > > I'm sure many would appreciate such a comprehensive large framework. > > I and many others in the node community would not. > > > > One characteristic of the node "philosophy" is freedom. The freedom > > to plug existing small modules together like a lego set. The freedom > > to easily write our own modules. The freedom to swap out modules for > > others as better ones come along. The freedom to make our > > architecture unique while not writing code from scratch or even using > > boilerplate. > > > > If I had to live within the constraints of J2EE or ROR or even > > Express, I would find another job. My architecture migrates quickly > > from project to project with each one more awesome than the last. Any > > existing framework would be outdated within a year as far as I am > > concerned. > > > > It is a new world.. > > A node.js "application server" is something Bert Belder and I have > been discussing. > > The proliferation (and wildly varying quality) of modules and > frameworks seems to be holding back node.js to some degree. I talk to > a lot of developers and it's one of the most common complaints: > "There's too much choice, we don't know what to use." > > The idea is to have a curated list of modules with appropriate > stability and support guarantees. If you find a bug, we'll make sure > it gets fixed in a timely manner; you won't be at the mercy of the > module author. > > That gives the developer a stable, known-good base to start out with > while preserving the freedom to use whatever he wants. It should also > take away the cold feet that some businesses have. > > -- > 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 > -- 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
