"If this one guy got hit by a bus, the software would fall apart."
lunduke.locals.com
lunduke.locals.com
> "SQLite is open-source, meaning that you can make as many copies of it as you want and do whatever you want with those copies, without limitation. But SQLite is not open-contribution."
This doesn't feel like a great example; it seems like if those 3 guys got hit by 3 buses, the source being available means that someone could fork it. (Assuming the license allows it.) At worst, folks could compile it for their own use.
Got some push back from one middle manager who said the complex driving their business line was understood by someone had been there by 20 years and was getting rebuilt in a year or two and there's no point in wasting anyone's time meanwhile.
I saw them a few months later where I got a free lunch as an apology. The only man who understood the complex code died of a heart attack while trying to prepare the next release. No one had a clue where to start making the required changes.
And you know what? That's not my only story of someone dying and no one being able to figure out the code that only they understood.
The maintainer of the xz compression tool didn't do anything malicious. This statement is incorrect and damaging.
I'm not on twitter but not my problem.
It’s more risky to run libsql because new features mean new bugs, but it seems worth it to me.
And how many of these projects couldn't be picked up and urgently patched if the proverbial bus does come along? Like it wouldn't be pretty, but would it be possible?
Or how else should I read the conclusion?