Becoming more politically active has been a massive source of community for me. And if community is already endangered (which isn't something I disagree with, by the way - so many people are inadequately supported), that's all the more reason we should find and build it.
A KDE dev mentioned on a podcast that issues related to Debian Stable get closed automatically on their bug tracker because fixes don't get backported :/
My wife was complaining about Windows issues so I ended up installing Fedora with KDE on her laptop. I would have preferred Debian but using Testing (as suggested by the dev) doesn't some ideal.
Debian Testing isn't really unstable - the dev wasn't exaggerating. But I'd also suggest Kubuntu (you can remove snap and all of its packages, and install Firefox and Thunderbird .deb's from the Mozilla repo)
You're thinking of Unstable (Sid). It's also not like Arch or Tumbleweed because it gets locked down during release freeze and then gets a ton of updates all at once.
It's been ages since I used VirtualBox and reading the following didn't make me miss the experience at all:
> Eventually I found this GitHub issue. VirtualBox 7.2.4 shipped with a regression that causes high CPU usage on idle guests.
The list of viable hypervisors for running VMs with 3D acceleration is probably short but I'd hope there are more options these days for running headless VMs. Incus (on Linux hosts) and Lima come to mind and both are alternatives to Vagrant as well.
I totally understand, Vagrant and VirtualBox are quite a blast from the past for me as well. But besides the what-are-the-odds bug, it's been smooth sailing.
> VMs with 3D acceleration
I think we don't even need 3D acceleration since Vagrant is running the VMs headless anyways and just ssh-ing in.
> Incus (on Linux hosts)
That looks interesting, though from a quick search it doesn't seem to have a "Vagrantfile" equivalent (is that correct?), but I guess a good old shell script could replace that, even if imperative can be more annoying than declarative.
And since it seems to have a full-VM mode, docker would also work without exposing the host docker socket.
Thanks for the tip, it looks promising, I need to try it out!
reply