On Mon, 20 Oct 2014 09:05:28 +0200, Sönke Ludwig wrote:
Am 12.10.2014 12:16, schrieb Angst:
[Subject], is it possible?
That way it might be easier to select all vibe.d plugins.That's an interesting idea, might make sense to add a section to each
package's page with all dependent packages.Also, ordering by "Most Depended Upon" might be nice.
I wanted to add this, or a combination with the download numbers as
"sort by popularity". I'm not sure when I'll get to that, though, as my
time for the open source projects will be extremely limited for the next
two or three months.
Looking forward to the next three to four months ;)
Wow, we have some catching up to do ;P
Node Packaged Modules
Total Packages: 99 528
https://www.npmjs.org/That's true, but if the (almost) exponential growth continues, we should
get some more impressive numbers in the not too distant future. But it's
the question if the number of packages is a good performance measure for
a package eco system. At least I would hope that D packages will have a
higher complexity (in the sense of amount of functionality) than the
average node.js package. Too many of those 100.000 packages are
absolutely trivial pieces of code.
Don't underestimate the usefulness of trivial/small pieces of code!
Take the grunt plugins:
http://gruntjs.com/plugins
You could classify a lot of these node modules as trivial: actual code (excluding tests) being around 100 lines. But they are well tested and without them grunt would not be possible.
Standing on tiny shoulders is still nice ;)