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 11 points 5 months ago (3 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

[–] [email protected] 24 points 5 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 3 points 5 months ago

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

[–] [email protected] 11 points 5 months ago (1 children)

You code in Java, of course you should self flagellate on a daily basis just for that. The entire ecosystem is completely fucked.

[–] sukhmel 5 points 5 months ago (1 children)

Joke's on you, I code in Rust

[–] [email protected] 5 points 5 months ago (1 children)

Then the joke is very much on us.

[–] sukhmel 2 points 5 months ago

To be fair, it wasn't ecosystem that made want to abandon Java, but now I can see it should've :)

[–] JackbyDev 3 points 5 months ago (1 children)

That is what they were getting at by some self flagellation can't hurt either. That sometimes "hating yourself" (adding dependencies) is worth it.

[–] sukhmel 1 points 5 months ago

I read it as "also throw in some physical pain cause just feeling bad is not quite enough" 🤔