Ah, I suppose I did word that poorly—I more mean that a significant breaking change (Casks that previously were documented as being excluded from auto-updating suddenly being auto-updated) which can occur silently is a rough end-user experience, even if the user explicitly opted into hiding hints.
You need to set HOMEBREW_NO_UPGRADE_AUTO_UPDATES_CASKS to 1, as alluded to by a hint when it (first?) occurs. This means if you have hints off (via HOMEBREW_NO_ENV_HINTS) then I suspect you can start getting this behavior without warning which is a bummer.
Tangentially related is NASA's open source GMAT[0] software which is more focused for calculating orbital transfers and the like. It's pretty fun to play around in.
Funny, I just started playing The Wise-Woman’s Dog yesterday—it really is excellent!
I’d also secondly endorse Dialog. It’s a really intuitive way to think about the game world as a whole without having to worry about Inform 7’s AppleScript-esque syntax. It’s also grown quite a bit since the community started their own fork: https://github.com/Dialog-IF/dialog
Even if the changes aren't "meaningful" (which it seems like they are), they still have an impact in how it makes the contributor more comfortable with working on the project. No new contributor is going to start with making massive patches without starting out with some smaller things to get a feel for working with the project.
I think it's probably less frequent nowadays, but it very much does happen. This still-active lawsuit[0] was made in response to LLMs generating verbatim chunks of code that they were trained on.[1]
For what it’s worth, I’m definitely leaning “Apple fanboy” and have been amenable to their past UI redesigns. This is the first that I truly think is a regression, and I immediately turned on Reduce Transparency after updating.