Do you mean the "this is where we're headed" comment? That's not agreeing with the direction.

The user who submitted the report that Stenberg considered the "last straw" seems to have a history of getting bounty payouts; I have no idea how many of those were AI-assisted, but it's possible that by using an LLM to automate making reports, they're making some money despite having a low success rate.

Every single time I've tried to work on a file using tabs, I've had to configure my tabstop to be the same width the original author used in order to make the formatting reasonable. I understand that in theory customizable tabstops is preferable, but I've yet to see it work well.

(For what it's worth, I think that elastic tabstops, had they been the way tabs worked in text files to begin with, would have been far preferable.)

Lots of acronyms no longer stand for anything due to losing their original associations. LLVM, AT&T, SAT (the test, not the programming problem), etc.

It's not so much a problem of there being things you "can't do" in other shells or older Bash, as that it breaks existing shell scripts, which is frustrating.

Right, that's the third meaning he cites for inheritance.

Definitely a good pick! I haven't learned it but I'm aware of some of its features, and it does seem promising.

Gotcha. Yeah, I feel similarly.

That, and the use of gitignore and other heuristics to ignore many files by default.

Plus, unlike grep, find is just...awkward. The directories to search must be prior to any search arguments (and . is not the default, it must be specified explicitly), and using a search pattern is treated as one of many special cases requiring one of a variety of flags rather than the obvious default operation.

It's a powerful DSL, but...not a convenient one by any stretch of the imagination.

The discussion was about sum types. The top-level comment, the one to which you originally responded, says:

It's a shame that sum type support is still so lacking in C++. Proper Result types (ala Haskell or Rust) are generally much nicer to deal with, especially in embedded contexts.

Was this analogy actually wrong, though? The internet is more like tubes than like trucks. Tubes captures the concept of bandwidth, as well as infrastructure needing to be in place prior to sending anything.

Well, in Rust, it's a sum-type, with functions that also let you use it like a monad instead of using explicit pattern matching.