Are you saying that the data has no value just because you can’t touch it?

It’s a company that targets kids. Their prices are ludicrous

How does any of this make a difference?

Also for a company targeting kids there sure are a lot of whiny adults in these conversations.

Why is everyone pretending like they have a right to play Nintendo games? Nintendo says they want $X, you say their game isn’t worth $X, so you get something different instead. What’s the problem?

If you’re at a flea market and can’t reach an agreement on the price, do you just throw a tantrum at the vendor and take their stuff anyway?

What’s even more funny is that you’re downvoted into oblivion, while Iheartcheese @lemmy.world gets praise for the same stance.

I guess “Fuck around and find out” doesn’t apply here.

Don’t forget to mention bootlicking in your replies, lemmys.

Ha! No.

To track changes to a project. You know, the thing Git has been made for.

“with glibc older than 2.31” ≡ “without glibc 2.31 or newer”

(In case you’re not referencing a misleading post title that’s since been edited.)

To answer the original question, even though @RedWeasel@lemmy.world’s advice really is superior:

All commands that can be executed via your shell must live in your $PATH or their subdirectories. You could enumerate all files in there, filter by being executable, and run them with the --help argument.

You can then filter these commands by their exit code. If --help is a recognized flag, the exit code should be 0. Otherwise it should be something else. (Running every command blindly might be a bad idea though.)

That Head First about design patterns actually takes heavy inspiration from the Gang of Four. I haven’t read both (only Head First), but I’d wager you don’t need to read GoF if you’ve read Head First.

Only the writing style… is somewhat cringy.

The single most bestest book that I wish my very first programming teacher would’ve hit me over the head with is “Code Complete 2” by Steve McConnell. I’ve only encountered it a few years into my studies, and time and again I thought: I had to figure this out myself!

It’s basically a collection of all the things you can consider, or think about, or do or do differently when programming. Nothing in there is revolutionary, and none of it is something you couldn’t come up with yourself, but I found it immensely helpful to have the content laid out in a structured way.

The Wifi thing is true enough.

Pinning your opinion to the top is an abuse of power.

A commit all by itself doesn’t mean as much without context.

Luckily a commit points to its parent, which means the context is inherently present. What’s your point?

Why would I not want to be able to apply a commit to any arbitrary branch?

Nobody said that.

Any shortcomings it may have aren’t necessarily due to a flaw in git.

True enough.

If I hand you a commit, you cannot tell which ‘branch’ it is on without searching the git history and hoping that you only get one answer. That’s a bummer if, for instance, you’re a github action and only get handed the commit. If it’s on the master branch, I want to do different things than if it’s a dev branch.

• A bug in the code controlling the Therac-25 radiation therapy machine was directly responsible for at least five patient deaths in the 1980s when it administered excessive quantities of beta radiation.
• Radiation therapy planning software RTP/2 created by Multidata Systems International could incorrectly double the dosage of radiation depending on how the technician entered data into the machine. At least eight patients died, while another 20 received overdoses likely to cause significant health problems (November 2000).
• A Medtronic heart device was found vulnerable to remote attacks (2008-03).

https://en.wikipedia.org/wiki/List_of_software_bugs#Tracking_years