Comment section reminds me of those for VLC. No clue why people complain about free stuff no one forces them to use. Like, just pay someone to implement DNSSEC if you really need that in curl, or write it yourself.
I guess this should be the revert he mentioned, for those interested:<p><a href="https://github.com/curl/curl/commit/c2df780a97d9913eb20a55d4caad95c29d688976">https://github.com/curl/curl/commit/c2df780a97d9913eb20a55d4...</a>
This happens every single time I make a new major release of a piece of software I maintain. There is always <i>some</i> mistake—even a typo in documentation—and it's the <i>tiniest possible mistake</i>, and there is always <i>only exactly one mistake</i>, but it's always enough to bug me so much that I have to make a patch release just to fix the one single mistake.<p>Some software developers are just cursed.
Looking at the comment section I feel assured that comments are a thing of the past. I wonder if those people would take the hurdle to send an email instead.
Bumping the major version for fun is actually a pain, since configure scripts set upperbounds on major versions to be future-proof, anticipating breaking changes. Now it's just another edge case to deal with, and old versions of curl-dependents to patch.
> Exactly why this was not discovered in our tests and CI jobs before the release we have yet to figure out<p>Oh, just because the tests can't imagine what the environment on all those hundreds of millions of client machines is :)
Bugs not being caught by tests seems like a big deal. I recently discovered a bug in the nodejs repl and couldn't get the tests to fail, even though there was a consistent infinite loop. It made me think about how many other tests are not surfacing bugs. It seems this is an example of at least one more.
uhhhh i wonder why the guy behind curl doesn't have a responsive website. Yeah I get it, he's a c++ developer and web design is not his job but it's not <i>that</i> hard