I've literally told my coworkers "I'm not saying we should never use dependencies. But every time you add a dependency, you should hate yourself a little bit more. Some self flagellation can't hurt either."

[–] sukhmel@programming.dev 11 points 10 months ago (8 children)

So, every time I use a library to recognize patterns on a picture, to interact with Kafka, do some SSL, or do database mapping, I should hate myself, noted

We did Elastic API integration in Java by creating and maintaining huge half-codegenerated transformer from code to Elasticsearch's JSONs, it was a pain and it was source of more than one error

Dependences should be reviewed and audited to make sure they do what you need and they are worth using. Just making everything in-house gets you nowhere most of the time

[–] aaro@lemmy.world 24 points 10 months ago (1 children)

Nobody is arguing that you should never depend on anything and create everything yourself, but adding a dependency for literally a one liner function is awful. Like one of the Go proverbs goes, a little copying is better than a little dependency.

[–] sukhmel@programming.dev 3 points 10 months ago

Yeah, there's mention of doing the opposite in C++ community in a neighbouring thread

load more comments (6 replies)

load more comments (7 replies)