en.wikipedia.org/wiki/Bus_factor is a thing that any GOOD project or IT department considers. How many of your staff can you afford to lose if they all happen to be travelling in the same bus, on their way to eat at the same place for lunch when an asteroid inevitably punches through said bus and/or diner.
‘Hit by an asteroid’ is a little unrealistic. Sentenced to prison for 15 to Life has happened in the Open Source community at least once before. The project I linked to had a Bus Factor of about one. It’s now ‘old code using outdated APIs’ and is considered obsolete.
I’ve personally seen legal and criminal issues for a single individual cripple IT departments before, meaning their bus factor was also way too low. I’ve been on trips that have been rudely interrupted by screaming executives when I came down out of the mountains into cell range because I was the only bus factor left on certain systems. Natural disaster, such as hurricanes, wildfires, and floods are very serious existential threats to even the largest of organizations.
Since Linux seems to be a good project, I can’t imagine that the discussion hasn’t been had, in public or in private. Millions of individuals and dozens upon dozens of big corporations depend on Linux, Open source and otherwise. If the bus comes for core maintainers or project leaders we have at least SOME backup.
I’ve been on trips that have been rudely interrupted by screaming executives when I came down out of the mountains into cell range because I was the only bus factor left on certain systems.
Wow, incredible management skills, genius move to treat your one critical employee like a piece of shit.
Yeah, that was close to the end of that job. I didn’t want to be there, and that particular manager was really upset that they couldn’t just eliminate those servers. He wanted his folks trained on them, but then refused to actually let them spend any time training on them. I was a scapegoat and took the severance deal ASAP.
when an asteroid inevitably punches through said bus and/or diner.
Or, you know there is a crash? Lol
I’ve never heard it with the asteroid explanation. But thousands of people die every year in car crashes. Most in single occupant vehicles, but a bus can be involved too.
“Brave Hero from Finland, you’ve been struck by a bus and are going to reincarnate into–”
“No I wasn’t. That bus CHASED ME DOWN two alleys, over a fire hydrant, into, and out of a Starbucks. It did NOT hit me. You just summoned me here.”
“Err… anyway, this world needs a hero to–”
“Write hardware drivers? A kernel module? Some inline assembly?”
"Err… the demon lord… er… "
“DID YOU EVEN MAIL THE LIST? Hah… Okay. Does this world have logic gates of any kind? I need to get this knocked out as soon as possible. I’ve got the entirety of the bcachefs patchset to review before 6.7 is in release.”
As much as I have issues with the snap implementation, I really want to live in a world where my base os is solid and everything else is easily updatable. LTS, with the latest apps.
Snap and flatpak achieve this, and I want more of that. Just less… frustrating. And less not-invented-here like.
Flatpak cannot do what’s discussed in the article. Snap can and it was started prior to Flatpak. If Flatpak was able to do what Snap can, you’d have half a point.
Flatpak cannot do what’s discussed in the article.
Nobody claimed 100% feature overlap. For regular GUI applications both work relatively similar, to the point that Snap now happily uses technologies developed for Flatpak, such as Portals.
it was started prior to Flatpak.
That’s irrelevant. One could just as well argue that Flatpak evolved from developments (OSTree, etc.) that are even older but that beside the point. Fact is that OSTree and Flatpak are vendor neutral and Snap isn’t. Attempts at vendor lock-in caused Valve leave Ubuntu and later choose Flatpak on SteamOS.
Snap has the ability to do the base system in a much more modular way and could be really cool for an immutable system. Forcing them on desktop users with their transitional deb packages and making it heavily integrated with only one repository really screwed it up.
Also I’m not sure about slow startup times. Are those still an issue? If so, then I would be sure to considet Ubuntu dead and not only not recommend it but actively recommend switching away from it.
Yes, they are still an issue. It is irritating enough that I have currently zero snaps and would rather build from source if snap is the only binary option.
That’s basically THE dealbreaker for snaps. Loop devices on lsblk? Most people don’t care and wouldn’t see it. Proprietary backend? Again, most regular people (Ubuntu’s target audience) do not care. So the slow startup time is THE dealbreaker.
what’s up with this? I see this school of thought bandied around quite a bit recently. wayland… it’s a protocol. do they hate tcp/ip too? can they boycott that instead?
For a moment I thought this post was about the LTT host. And was like they could replace him with any of his doppelgangers in the group and no one will notice.
That’s because even a grey market Windows key costs US$20 nowadays and that’s over ₹1,600. For comparison purposes, the largest Indian banknote is ₹500.
…but not legal. Being poor doesn’t necessarily mean you’re inclined to break the law. Besides, Linux is useful if you perhaps want to later get a job in the tech field.
You’re not breaking the law, you’re breaking a software license agreement. That does not automatically make it a crime, at least, that would depend on your exact local laws, and the lawyer’s interpretation of it - in many cases the actual wording around this is ambiguous and could be argued both ways. A better term for it would be a “legal grey area”, which means if you’re a company then don’t f*** around with it, and if you’re just a random user then no one gives a f***.
In any case, if those scripts were truly illegal, then the Microsoft-owned Github wouldn’t host them in the first place. Clearly Microsoft themselves don’t have an issue with it, so why should anyone else care about it?
Yes, you are breaking a law. Copyright infringement in this manner is an offence under the Copyright Act 1957 punishable with up to three years imprisonment and a fine.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.