News for hackers. Stuff that matters.
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.