Hacker News new | past | comments | ask | show | jobs | submit login

Minimalism has a cost. http://npm.broofa.com/?q=zero



It's worth noting that (for now) npm.broofa.com includes `devDependencies` in it's graph. Zero doesn't have any production `dependencies`.


Ignore that. Apparently I don't know my own code. It just looks at `dependencies`. :-p

That said, it looks like the latest (not yet npm-published?) version of zero has moved all the dependencies to `devDependencies`.


It's not that bad since it's an application (not just a library) that basically exists to glue those modules together.


Standing on the shoulders of giants :)

You will eventually be adding all those packages when you develop a production-grade React / Node app anyway.


Perhaps this should be done gradually and thoughtfully, rather than pulling half the internet into each minimalist app out there.


Welcome to the world of node.


This is nothing to do with node. This is poor programmer decision making. You can build great node apps with a real minimalist approach. Holding up projects which pull in half of npm as "the world of node" is like holding up a hot and ready 5$ pizza and saying all Italian food is bad.


I think the point is that this is almost encouraged in the node ecosystem, while in most other language ecosystems I know of it wouldn't be.


Most other ecosystems inlcude more batteries (e.g. PHP). That is why you have to update this ecosystems with all their modules. The problem is, if the core has a bug, ALL apps in this ecosystem has the bugs.

node includes not everything and concentrate on the core. If modules have bugs, not all apps a compromised.

It is a fundamental design decision, if you not like it, don't use node.

You can include all dependencies manually and update them manually, nobody keeps you away. But have fun to update all your deps.


Encouraged by who? I see the same people which used to install jQuery or WordPress plugins and were able to get janky but working sites. But prolific module authors and node core contributors don't promote these approaches.

Maybe if you listen too much to twitter "thought leaders" you might get this impression, but we are all aware of the problems with social media platforms...


Well, considering the amount of dependencies in popular projects like CRA that was highlighted here a few days ago I don't think it's unreasonable to extrapolate to the general ecosystem. Of course there are module authors and devs doing it differently, but in general most node projects I see are more dependency-happy than projects I see in other languages.


Give people a useful tool (npm) and they will muck it up. This is both the best and worst part of the general node ecosystem. The issue is people saying things like "that's just node". It is not node, it is the ease of use and popularity meaning there will be more of these examples. If you care to make high quality use of the platform and tools you can, but that means not following the crowd.


Agreed, but for whatever reason it seems more prevalent in the node ecosystem than in others (even when comparing high-profile projects).


thank you...your comment is just awesome!!! i thought i was alone in understanding the real meaning of being a "minimalist" ;)


This is why we need tree-shaking and build-time optimizations to kill the unnecessary.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: