News for hackers. Stuff that matters.
Re:The Node.js Community is Quietly Changing the Face of Ope... by LargeWu on Tuesday April 16, 2013 @09:54AM (#5558041)
If it's trivial to create packages, I suspect we'll end up with a lot of trivial packages.
Re:The Node.js Community is Quietly Changing the Face of Ope... by philodespotos on Tuesday April 16, 2013 @10:31AM (#5558268)
Which is perfectly fine. I mostly want to be able to trivially use packages which solve my trivial problems, so I can move on to something more fun.

The issue eventually becomes a one of search; when I'm looking for a package, how do I know which are maintained, which never picked up broad adoption, etc?

Between the npm registry[1] and node-toolbox[2], there's already decent visibility into it. I often find the output of 'npm search' daunting to the point of mental paralysis, though.

[1]: eg, if I need a redis client, I can see the redis project is active and broadly used: https://npmjs.org/package/redis

[2]: similarly, http://nodetoolbox.com/categories/Redis

Re:The Node.js Community is Quietly Changing the Face of Ope... by jerf on Tuesday April 16, 2013 @10:33AM (#5558277)
Now, take that observation and go back and read the original post.

I'd observe that the new languages all seem to have been accelerating their rate of package production over time. This is probably because over time the set of easily-copyable packages goes up. It's much easier to release a simple Rails clone after Rails has made the idea popular. It seems like every year there's another Brilliant HTML Templating Idea, and a new language can rapidly develop clones of the entire history of HTML templating ideas, whereas one that was new ten years ago had a much thinner pool of copyable ideas.

This isn't a criticism of Node (which I am certainly prone to, but this is not one of those times), this is an observation that it seems like each new language rapidly builds up packages faster than the last one and this probably isn't actually an attribute of the language.

Re:The Node.js Community is Quietly Changing the Face of Ope... by lmm on Tuesday April 16, 2013 @11:21AM (#5558630)
Do you know of a wicket-like approach to "templating" in python (or indeed anything other than java)? I'm currently in the process of building my own clone in python, and I feel really bad about doing so, but it's so much better than all the approaches to html generation in python that I could find that I'd rather do this than struggle with vanilla django templates, or even genshi.