This meme has successfully inspired me to rewatch Sealab. Thanks
Why, is it impossible or difficult to enforce?
Not sure, that’s why I asked out of curiosity. But I would assume so; it’s very easy to get WireGuard setup on a Raspberry PI or just about any SBC. For example, you could setup a SBC with a usb WiFi adapter, travel to a state where VPNs aren’t banned, connect to public WiFi and with a little additional config (changing ports), you’re good to go.
Just curious, but how would that be enforced?
For-gy-o
Now there’s a winner. F-Orgy-O. Like a Federated Orgy.
I can’t remember how I rescued it now but managed to get it back without a reinstall
You could’ve booted into a previous generation where you still had all those things on your system. The glory of atomic distros :)
I did for some time. There’s beauty in the simplicity and flexibility of Alpine, plus BusyBox is great once you understand all the weird quirks between it and coreutils
. As unpopular as it might be, I actually really like OpenRC. Alpine feels pretty close to BSD if you’re familiar with that family of operating systems. These days I use it for just about all my servers save for a few Nix boxes.
If you decide to explore this route, here are a couple tools I found useful at the start:
Also might behoove you to check out Alpine community’s documentation on chroots in case you need specific software that isn’t available otherwise.
Since no one answered you here, I’ll say distrochooser.de isn’t bad at all. For the new linux user who is comfortable enough trying new things, I think it’s perfect. It does lose its usefulness if you’ve already tried all of the options it offers, but at that point you probably don’t need distrochooser anyway.
The Asahi Linux project provides a Fedora-based experience for people using Apple Silicon. It works well for the most part but there are features that are still being developed.
As for Windows, I don’t know of any methods to get Windows running outside of macOS, but many people utilize Parallels for Windows apps or the desktop experience.
That’s correct. This simplifies the dependency management system because not every distribution ships with every version of every package, so when software requires a version of a package that the distro dosesn’t ship with or have in its repositories, the end user has to either build the package from source, or find some other way to run their software. Flatpaks developers will define the versions of dependencies that are required for an application to run and that exact version is pulled in when the flatpak is installed. This makes the issue of every distro not having every version of every package moot.
They don’t have to, no. But they absolutely should.
Sometimes, yes. Or the software is using a dependency that is so old that it’s no longer included in a distro’s package repositories.
I would say they’re suited to different purposes.
Docker shines when availability is a concern and replication is desired. It’s fantastic for running a swarm of applications spread across multiple machines automatically managing their lifecycles based on load. In general though, I wouldn’t use Docker containers to run graphical applications. Most images are not suited for this by default, and would require you install a bunch of additional packages before you could consider running any graphical apps. Solutions to run graphical applications in Docker do exist (see
x11docker
), but it doesn’t really seem like a common practice.Flatpaks are designed to integrate into an existing desktops that already have a graphical environment running. Some flatpaks include the packages required for hardware acceleration (Steam, OBS) which can eliminate the need for those packages to be available via your distro’s package manager.
What this means is that a distro like Alpine Linux that doesn’t have an
nvidia
package in its repos can still run Steam because the Steam flatpak includes thenvidia
driver if you have an nvidia GPU installed.¯_(ツ)_/¯ It’s a tool. Use it when it’s useful, or don’t.