News for hackers. Stuff that matters.
Re:Responsible JavaScript: Part I by hobs on Monday April 15, 2019 @10:15AM (#19665439)
Taking on a huge amount of dependencies only (potentially) makes your life easier up front.

You now get to experience all bugs and side effects for all projects you now took on "due to ease."

You now effectively maintain all those projects, instead of your own. You cannot go to your customers and say "well this library isnt working so neither is our website, and we can upgrade without it."

Re:Responsible JavaScript: Part I by jamescostian on Monday April 15, 2019 @11:36AM (#19666077)
You also cannot go to your customers and say "well instead of using a popular library, we used our own and it broke and so did your site"

And more importantly, NIH leads to on-boarding issues. Many, many people are React/Angular/Vue developers, but how many are $INTERNAL_RECREATION_OF_REACT developers? By creating a new framework, you waste money (not just on reinventing the wheel and fixing bugs in your new wheel, but also on having every new-hire take even longer to get productive)

Re:Responsible JavaScript: Part I by userbinator on Monday April 15, 2019 @10:07PM (#19670553)
Code that you've written also tends to be code you have an understanding of, and thus much easier to debug than a maze of third-party dependencies.

The extreme aversion to "reinventing the wheel" leads to things like left-pad.