There's a very complex and intricate law to the internet. One of the rules of this is: if you can bring in a code library, it stops you having to write code.
No matter how many problems the code library you bring in causes you, it's better than learning the language yourself.
If you think otherwise consider: yes, sometimes it really is better to bring in a code library. Maybe it's a tiny library that cleverly wraps something notoriously confusing up in a package that makes things so much easier. Maybe it's doing cryptographics that you will never in your life have the time to learn the mathematics to do properly.
Or many it's a random library you brought in because there was buzz around it without really knowing why, and some idiot thinks it's just garbage. What's their deal? Maybe they think you're bringing in moment.js to format a date that's now native to the TypeScript compiler you're using just because you don't know any better. Resist these people.
Who cares if 90% of imports into a package.json are not needed. Or 99.2% of useless dependencies are created by people with loads of experience who should know better about these problems but are too jaded to care about the issues they create. The point is if you're senior enough to fix these things but don't want to, it's not your problem. If you're a junior, who the hell cares what you want, just do what they say for the lord's sake.
Top comments (0)