I agree! However in many cases, these edge cases (I'm not speaking of curl now) are not needed for my personal use. E.g. if I use linux/windows/os, I do not care about how my tool behaves on the other os, I do not want to support all kind of hardware etc. If I am the only users, I can prune these use-cases (and features I mentioned in the post) significantly. E.g. I reimplement a subset of vim at the moment, I do not use LSPs or syntax highlighting in my work, I do not need to implement support for them in my editor.
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.
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.
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.
Got mine (13th Intel Core Ultra Series 1) and very happy with it.
Re modular ports, I don't think they are super useful after you've selected your configuration, but being able to have a custom port selection is very nice.
I am using Arch, btw, and everything has been working well so far. I thought there were some drivers issue, but turned out it was due to my bootloader setup (https://yobibyte.github.io/kernel_update.html)
> the biggest (and probably the only) beneficiary of such structured notes is the note-maker.
I would probably agree with the "biggest", but disagree with the "only":
* The readers might use a note as an extended abstract when selecting a paper to read. This is like a short conference talk which is for advertising the paper and inviting people to the poster session.
* The authors get feedback about their research, and some of them engage in a discussion as well.
Having said that, I agree that taking your own notes is better for you.
