9 ms·
Curl 8.0.1
- st_goliath 4y agoI guess this should be the revert he mentioned, for those interested: https://github.com/curl/curl/commit/c2df780a97d9913eb20a55d4caad95c29d688976 https://github.com/curl/curl/commit/c2df780a97d9913eb20a55d4...
- danwee 4y agoI'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)
- shawabawa3 4y agoIt was a performance optimisation, so I suppose it should be covered by existing tests as there should be no change in behaviour
- danwee 4y agoAh, good point!
- withinboredom 4y agoThis looks like an integration point, which are pointless to test.
- e12e 4y agoIt did in-fact have test coverage, from tfa: > Apart form the little bug that caused it to crash in several test cases. (...) > Exactly why this was not discovered in our tests and CI jobs before the release we have yet to figure out, but it is certainly more than just a little disturbing.
- hyperman1 4y agoI 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.
- eptcyka 4y agoWorking on new, small bits of software often implies that a single commit will be more relevant to the rest of the codebase. The more code there is, the less any one particular line, on average, would matter.
- vocram 4y agoMaking smaller and atomic commits makes them more easily reversible.
- Cthulhu_ 4y agoAtomic meaning they can be reverted on their own; I'm sure plenty of people make the mistake of making small commits, but not atomic commits. If your git history looks like a work log, you're not writing atomic commits. And people should get comfortable with git commit --amend and interactive rebase.
- SushiHippie 4y agoShould've instantly bumped it to version 9.0.0 instead of 8.0.1
- artemonster 4y agoSince 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“
- danielskogly 4y agoI think the parent might be referring to this: https://news.ycombinator.com/item?id=35228608 https://news.ycombinator.com/item?id=35228608
- aew4ytasghe5 4y agoThe joke is 8.0.0 did not break API.
- hyperman1 4y agoTo never use the first release of any major version is confirmed as a good policy again ;-)
- jve 4y agoIs there a commitment from curl to use semver? If not, all the discussions about why the bump to v8 is void. We know a huge project that doesn't stick to semver and update major version whenever they want: Linux Kernel. Ofcourse we wish everyone would use semver...
- deleted 4y ago[deleted]
- reisse 4y agoIf Linux used semver, it'd never go past 1.x. Public kernel API never breaks, ever. So what's the point for semver?..
- amelius 4y agoI personally use wget because you can download files without any extra flags.
- KyeRussell 4y agoYup. curl for when I want to see it, wget for when I want to save it. No shame.
- layer8 4y agoOr `wget -S` when you want to save it AND see the headers.
- stonewhite 4y agoCurl 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
- msravi 4y agoalias wget="curl -sL -O --no-clobber" Update: Based on comments from @xorcist and @stabbles: alias wget="curl -fLsS --no-clobber --remote-name-all"
- amelius 4y agoOr just use wget ;)
- msravi 4y agoThe best thing about curl is that developer tools of browsers (firefox for example) have a convenient "Copy as curl" feature that mimics the web request. The reason there isn't a "Copy as wget" option, I think, is the level of control that curl allows so the request can be tailored to exactly mimic the browser. But when you want to recursively download a website, of course, nothing better than wget. curl doesn't support that, and you'll need to parse and fetch the urls recursively yourself with a script.
- favaq 4y ago[flagged]
- yokoprime 4y agoWhat does this mean? Curl is over 25 years old, its not like this is the latest hotness.
- reportgunner 4y agoI just click the "hide" option for all posts I don't like, it works well.
- KyeRussell 4y agoWhat’s important is that you’ve clearly established that you’re a superior free-thinker.
- deleted 4y ago[deleted]
- junon 4y agoRight, 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?
- stabbles 4y agoBumping 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.
- sethammons 4y agoI'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 https://github.com/grpc/grpc-go/issues/3798
- tqkxzugoaupvwqr 4y agoIf you read the first comment, you’ll see the API was documented as being experimental. https://github.com/grpc/grpc-go/issues/3798#issuecomment-670108443 https://github.com/grpc/grpc-go/issues/3798#issuecomment-670...
- sethammons 4y agoI'm clearly in the camp of "you can add and depreciate (experimental) features all you like in minor versions, but you should only remove them in major versions" camp. See the discussion on semver and experiments: https://github.com/semver/semver/issues/238 https://github.com/semver/semver/issues/238
- dtech 4y agoThat's the rule for normal features, that would mean there is no meaningful difference between stable and experimental parts of an API.
- vlovich123 4y agoHyrum’s law. Rust mostly gets around this by requiring you run the nightly compiler and library in addition to explicitly opting into experimental pieces.
- nottorp 4y ago> 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 :)
- rkta 4y agoLooking 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 4y agoThe 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/ https://daniel.haxx.se/blog/2021/02/19/i-will-slaughter-you/
- rkta 4y ago> one comment, that the moderator didn't even see fit to remove. Ain't much. It's not only about the comments we can see, but also about those comments that get filtered out by the moderator > Also funny that you wonder if people would take the hurdle to send an email instead. Of course you also get non-friendly emails. I was wondering if the people that leave those comments would send an email instead.
- anoonmoose 4y ago> filtered out by the moderator If that's what he left in and responded to, what do you think he's taking out? > wondering if the people that leave those comments would send an email instead The evidence presented is that he gets abusive emails with a comment section...why would he get less emails if he closed the comment section?
- rkta 4y agoOf course he will not get less email when closing the comment section. The question was if he will get more email abuse when closing the comment section.
- deleted 4y ago[deleted]
- LoganDark 4y agoThis 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 4y agoYep, 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.
- more-coffee 4y agoAnd that's why I never trust/use x.0.0 releases because they must have missed something :)
- thih9 4y agoIs 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.
- LoganDark 4y agoI review it 10 times before I make the release and spot nothing, but then spot something only immediately after I release it. Just like how I can only spot typos in emails after I've already sent them.
- jansommer 4y agoComment 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 4y agoTried 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 4y ago> 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.
- Cthulhu_ 4y agoRoads are not free, we pay taxes so that the government maintains them, like every other public utility. Open source software is not a public utility and not paid for with tax money, therefore your analogy is flawed.
- leshenka 4y agouhhhh 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 4y agoLMAO
- harrisi 4y agoBugs 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.