Am I the only one that looks at some of these graphs and thinks OMG THE BLOAT! and runs in the opposite direction? These days with a lot of app dev the deps go deep and a tool like this draws a very informative picture.
I used to be worried by amount of dependencies too, when I was transitioning from .NET stack to js. Until I realized that each module is usually very small, doing only one thing, and most of the time doing it well.
Now I'm thinking of them in terms of code reuse. Code reuse is good
The goal was to illustrate how unique dependencies could be packaged separately for progressive loading while navigating single page javascript applications.
16 comments
[ 3.3 ms ] story [ 39.6 ms ] threadWhat would be a connection between two maintainers? If their packages depend on each other, or if they co-maintain a package?
Am I the only one that looks at some of these graphs and thinks OMG THE BLOAT! and runs in the opposite direction? These days with a lot of app dev the deps go deep and a tool like this draws a very informative picture.
I used to be worried by amount of dependencies too, when I was transitioning from .NET stack to js. Until I realized that each module is usually very small, doing only one thing, and most of the time doing it well.
Now I'm thinking of them in terms of code reuse. Code reuse is good
The goal was to illustrate how unique dependencies could be packaged separately for progressive loading while navigating single page javascript applications.
If you're interested in the real deal though, checkout http://stealjs.com/docs/StealJS.why.html#section_FasterLoadi...
Jade template engine: http://npm.anvaka.com/#/view/2d/jade
Hogan.js template engine: http://npm.anvaka.com/#/view/2d/hogan.js
Found generator-angular-fullstack so far, with 142 nodes. http://npm.anvaka.com/#/view/2d/generator-angular-fullstack
it's also not very googleable and it's poorly advertised, but it's also cool.