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

It's both good and bad; depending on how much care is taken in selecting dependencies.

It's hard to use a lot of dependencies, regardless of their quality, without introducing bloat. Lots of redundancies.

For example, each dependency may have its own messaging or thread management system, or its own memory management system.

Or it may include other dependencies that have their own "special sauce."

For myself, I use lots of little packages; mostly written by Yours Troolie, and only occasionally use third-party dependencies.

Each of my packages is usually crafted towards a certain discrete function, and has its own project lifecycle. I think that's a good thing about using dependencies. I believe that modules with encapsulated lifecycles are a good way to ensure quality (or not, if I "choose poorly," as the Knight Templar said in the Indiana Jones movie).




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

Search: