See Zed ‘Em?

She was also part of the team that discovered and coined the term “bug” in relation to a computer defect. She didn’t invent the term herself directly, but she was part of the team that did.

One other thing you may have to do if you have contributors who have also committed code is to get their permission to change the license as well, as the code they committed may still be under their copyright and not yours, and they can choose to allow their code to be relicensed or not. Some projects use a contributor release to reassign copyright for contributions for reasons like this, for instance. This is partly the reason why the Linux kernel has never changed to GPLv3 and still uses GPLv2 (and also because Linus just doesn’t like some provisions of the GPLv3) — it would be pretty much impossible to get everyone who contributed code to a project as large as the kernel to agree to a license change. Any code that couldn’t be changed would need to be extracted and rewritten, and that’s not going to happen given the sheer size of the code base.

If you don’t have other contributors then you’re home free. You can’t retroactively change licenses to existing copies of the code that have been distributed, but you can change it going forward.

macOS has something to this effect where if it detects too many kernel panics in a row on boot it will disable all kernel extensions on the next reboot and it pops up a message explaining this. I’ve had this happen to me when my GPU was slowly dying. It eventually did bite the dust on me, but it did let me get into the system a few times to get what I needed before it was kaput.

Bought a new computer, threw the old one out.

Use etc-keeper, saves everything in a git repo and integrates with a bunch of package managers. Been using it for decades it feels like now.

Ligature, not lineature.

Exit codes from processes are damage points that you take against your HP. When your HP runs out, the distro reformats itself to a clean state.

I wouldn’t say quite the same root cause — the xz back door was clearly intentional, but I don’t recall the Heartbleed bug having been intentional, and developer responsible has denied allegations to that effect. There can be no doubt in the xz case of malicious intent.

That’s easy, just create new accounts every time you login.

Why wouldn’t you just create a GUI interface in Visual Basic to track their IP addresses tho?

How do you know that deleting anything on Reddit actually deletes anything? It might just hide the content but soft delete it in the database, which means you may not be able to see it anymore but they can still use it for whatever.

Perl I believe is where the programming adage of TMTOWTDI comes from — There’s More Than One Way To Do It. Python was an anathema to that ideal, where TOOWTDI — There’s Only One Way To Do It, or at least one ideal way

I don’t know man, speaking as someone who lives in a hurricane-heavy locale we have to deal with broken windows due to storms with some regularity.

K&R for life

Better not tell them about daemons I guess.

I once fixed a bug in credit card payment form because someone had gotten some formatting character screwed up and used a capital M in some place where a lower case m should have been. Since it was a payment system they couldn’t take payment for a while whilst that was screwed up. I was contracting there and happened to notice it. Sometimes all it takes is one character.

To be fair, sometimes I look at my own code and think it was done in another language, and I only know English.

Not sure. He’s a KGB-educated Russian billionaire oligarch so take from that what you will.

It was literally Eugene Kaspersky, founder and CEO of Kaspersky.