No? The article literally explains that it’s for something else?

It only limits you if you expect things to work exactly the same as with any other distro. If you spend some time reading up on how it expects you to solve different tasks, it doesn’t limit you for 99+% of scenarios.

The shitty news here is if you want a machine you’re doing software dev on you’re going to need to figure out the nvidia driver shit, which is a pain in the ass but if you’re a software developer you should be able to do it.

The dev-focused atomic Fedora variants solve all Nvidia issues for you, there’s no reason why you should trouble yourself with it.

Could be an SELinux issue. Look up mounting with the :z/:Z option.

If your country can’t prosecute the leader of an insurrection in four years and has to let him run for president again, it’s already a failed state.

Let’s be real - if they get a majority, the Dems will find a way to delay the impeachment until the end of his term, in the hopes of getting more votes in 2028. They already pulled the same shit twice.

Unfortunately Sync has been abandoned, so you might want to look for a new app soon.

Snaps are bad for two reasons:

1. The backend is proprietary & the client doesn’t support other backends without modifying the source code
2. For some packages, doing apt install installs the Snap instead

There’s no good reason for either. Canonical is simply setting things up so they can squeeze money out of their users by enshittifying over time.

Because by the time I use awk again, I’ve completely forgotten that it supports this stuff, and the discoverability is horrendous.

Though I’d happily fix it if ShellCheck warned against this…

I hope they like it

Yes, it’s Volition.

Why?

You can’t run apt-get etc. on your host, but the idea is that you create containers with whatever distribution you want through distrobox and run your commands in there. In effect, there’s pretty much no difference, especially if you set your terminal up to open into the distrobox.

No, it’s not a thing, it’s literally what I described earlier - QEMU in a Docker container. That’s why the Dockerfile imports files from QEMU, and why the entrypoint starts the VM using QEMU. The project this whole thread is about uses dockur/windows as the base.

It will never be a thing.

That will unfortunately never be a thing. They could theoretically do a “Docker machine” like setup to support actual Windows containers, but there’s probably not enough interest in that.

Docker and Podman can’t run Windows VMs by themselves. These containers use QEMU, so it’s essentially a pre-made setup for what you already had.

I haven’t yet run into any piece of software that’s fundamentally incompatible with the immutable model thanks to distrobox. This also means I don’t have any packages layered, so updates are very quick.

It does, but it doesn’t look like Kent will get his shit together. He cannot accept that he might be in the wrong.

Me following the recent bcachefs drama

(Kent is objectively in the wrong & slightly bat shit, if you follow his many discussions in various forums where he defends himself)

I’ve had Macbooks also fuck up their sleep state, only waking up after a full shutdown.

Maybe the M-core series is better? I don’t know, haven’t tried any of those.