[panny]

I'm thinking of something like curl specifically where the edge case isn't your machine, it's the machine you're talking to. Can I write my own curl-like downloader in a few hundred lines of code? Yes. Is it going to work first try with a 30 year old apache file server? Probably not. Do I want something that works "good enough" which breaks when I'm in the middle of a time crunch... or do I want something production tested that's probably not going to fail on me at the worst possible moment.

I'm willing to accept a little bloat and pass on inventing wheels myself if I can grab something reliable off the shelf. I don't think that makes me less self reliant.

[balder1991]

Yeah, I don’t think the curl example was meant as a knock against curl or advice not to use it. I think any command-line user would agree that curl is not bad or bloated software, which is what they criticize.

The point seemed to be that even a rock-solid tool like curl started out tiny — just a few hundred lines — before growing to cover all the edge cases you’re describing. It’s more about showing that you can start with something simple for your own needs and customize it without depending on someone else.

[panny]

There's the old saying, there are three types of people. Dumb people never learn from their mistakes, smart people learn from their mistakes, and wise people learn from the mistakes of others.

I try to choose wise, even if someone will later throw shade on me for not being "self reliant" or some other insult of the day. If my goal is to write a better libcurl, then that's what I'll work on. But that's basically a solved problem and working on that doesn't seem like the best use of my time.