Curl 8.0.1

[jansommer]

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.

[m4lvin]

Tried to leave a friendly comment, but apparently the database is hugged to death...

> Replace this text with the error page you would like to serve to clients if your origin is offline.

[Joker_vD]

> No clue why people complain about free stuff no one forces them to use

Just like roads. Nobody forces people to use them, you know; sure, some people might want to use them, to go for some place for some other non-road-related business but that's just their problem.

On a more serious note: people complain about "stuff" when they try to use that "stuff" to do something and it doesn't work no matter whether it's free or not, it's just human nature. As for "forced to use"... if you need to make a network request from command line, the options are basically curl or wget. Neither of them support your use case? Well, you can always just give up and not do whatever you intended to do, nobody forces you to achieve things anyhow.

[st_goliath]

I guess this should be the revert he mentioned, for those interested:

https://github.com/curl/curl/commit/c2df780a97d9913eb20a55d4...

[hyperman1]

I always find it a small miracle that you can yank an individual git commit out of a program, and end up with a working program. If I commit anything, follow-up commits quickly make the original quickly a hard requirement.

Maybe it is a sign of bigger and more stable source code, that individual commits influence each other less.

[danwee]

I'm a nobody, but surprises me that the revert (and so the original feature) didn't include any tests. I always imagined that a project like curl (no deadlines? no pressure? no bosses?) would lead to people to work on it at their own pace (so more tests maybe? Maybe not, I don't know)

[LoganDark]

This happens every single time I make a new major release of a piece of software I maintain. There is always some mistake—even a typo in documentation—and it's the tiniest possible mistake, and there is always only exactly one mistake, 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.

Some software developers are just cursed.

[junon]

Yep, have definitely done this once or twice with Chalk. I don't recall a time that a X.0.0 wasn't immediately followed up with an X.0.1 release for some dumb mistake I made.

[thih9]

Is not a curse, it’s probability and statistics. If you make a major release, you touch a lot of places and there’s a higher likelihood of introducing a bug.

[rkta]

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.

[anoonmoose]

The death of the comment section has been greatly exaggerated...one comment, that the moderator didn't even see fit to remove. Ain't much.

Also funny that you wonder if people would take the hurdle to send an email instead. In this particular case, the author has in fact written about the torrent of email abuse he faces on multiple occasions, for example here [1]. Is his 2021 post evidence that email is a thing of the past?

https://daniel.haxx.se/blog/2021/02/19/i-will-slaughter-you/

[edent]

From experience, yes. "Those" people will send an email, add you on LinkedIn, and call you landline if they don't like the content of your blog.

[TechBro8615]

You mean the single flagged comment? There are more comments talking about the bad comments than there are bad comments.

[stabbles]

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.

[Karellen]

I thought the 8.0.0 was justified by dropping support for platforms without 64-bit integer types?

Dropping support for a group of platforms is definitely something I'd consider a breaking change.

[sethammons]

I'd rather deal with that than the team at Google who maintains the grpc Go library who are more than fine breaking the public API in minor changes.

https://github.com/grpc/grpc-go/issues/3798

[justeleblanc]

That's only true for a small portion of software released. I have an idea about where this fixation in semver comes from, but I can't really believe that everyone here is a web dev who wasn't around before semver started getting traction.

[avgcorrection]

It isn’t “for fun”.[1] The project apparently just doesn’t support the versioning scheme that you allude to.

If you want this project to use a particular versioning scheme then you should just argue for that directly.

[1] Other than this snippet :) : “on curl’s 25th birthday made it extra fun”

[SushiHippie]

Should've instantly bumped it to version 9.0.0 instead of 8.0.1

[rwky]

Or copy what Windows did and jump straight to 10!

[artemonster]

Since there is no /s at the end I will assume it was not a joke. Most versioning schemes assume logic behind bumping numbers, please check for example „semantic versioning 2.0.0“

[nottorp]

> Exactly why this was not discovered in our tests and CI jobs before the release we have yet to figure out

Oh, just because the tests can't imagine what the environment on all those hundreds of millions of client machines is :)

[harrisi]

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.

[amelius]

I personally use wget because you can download files without any extra flags.

[stonewhite]

Curl more equivalent to cat as a unix tool, making it easier to use in pipes. If your only use case is downloading then wget might look more practical

[KyeRussell]

Yup. curl for when I want to see it, wget for when I want to save it. No shame.

[msravi]

alias wget="curl -sL -O --no-clobber"

Update: Based on comments from @xorcist and @stabbles:

alias wget="curl -fLsS --no-clobber --remote-name-all"

[kevincox]

    curl https://example/file >file

[thih9]

But what if you want to send an API request?

[yokoprime]

What does this mean? Curl is over 25 years old, its not like this is the latest hotness.

[junon]

Right, but targeted "fuck this guy" comments are acceptable.

What did Drew Devault ever do to you? He's a smart guy and quite nice to talk to. What's the problem?

[KyeRussell]

What’s important is that you’ve clearly established that you’re a superior free-thinker.

[reportgunner]

I just click the "hide" option for all posts I don't like, it works well.

[leshenka]

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 that hard

[garritfra]

LMAO