It will work for a while but it will lag behind in terms of integrations, features, and eventually it will also reach EOS/EOSL and might not even get bugfixes backported anymore.

KDE Plasma 6.8 will be the first KDE Plasma release to remove the X11 backend, going Wayland-only. In KDE Plasma 6.8, there will be no X11 session on the login screen.

This is a big change. I will now need a separate DE for x11.

I only used something similar to mess around with Hytale modding a bit, but it was only easy because there was fully ready-to-use premade solution. But in general, if you’re willing to go that way, I think the most simple option would be to create a distrobox with ubuntu/debian/fedora/arch (depending on which distro covers things you need better), install vs code there (using native package manager of given distribution), and then distrobox-export VS Code from that distrobox. Then you can simply manage everything inside of distrobox using full power of distribution you chose. To make things even better, distrobox has automatic passthrough of most hardware. For Nvidia in particular, you need to pass flag “–nvidia” when doing “distrobox-create”. After that, you can even use game engines like Unity or Godot from distrobox with full GPU passthrough.

Well they basically forked Bazzite DX image and customized that… The hyprland fork author stopped maintaining it 8 months ago so it’s not gonna work anymore with any recent Bazzite versions. So what they did is how Bazzite itself was created in the first place - by forking Fedora Atomic image and customizing it. I wouldn’t really count this as “Bazzite supports other DE/WM”, but yeah, if someone decided to go this far and make a fork like this then great, you can use it and hope they’ll keep maintaining it.

You can write your own systemd services and you can customize your Plasma using panel colorizer. You can go a bit further and rpm-ostree install kvantum and get even more ricing freedom. You can’t however make it use other init system or other DE/WM. It’s still quite good for what it is.

I kinda agree, but it can also be pain in the ass. For example, using flatpak VS Code is massive pain in the ass. You end up needing to do tons of tricky workarounds for all kinds of language server/formatter/etc addons to work properly. It’s okay when you only need to do it once for a single language (Rust, for example), but it becomes very annoying when every new addon you install is highly likely to need you to write some flatpak-spawn based wrapper scripts in ~/.local/bin or whatever extra userspace bin folder you added to your PATH.

This is one of the reasons I switched to Gentoo in early May. The way systemd managed that userfield situation wasn’t nice at all. There is no reason to assume they will not do the same when asked to implement something worse. On the other hand, if they declined that change, it would mean they would most definitely decline a worse change. It is a great motivation to move away. There are way more reasons to move away from systemd, yet I wasn’t aware before this happened, so it was also a trigger to do some deeper research on other technical concerns as well.

Can’t wait until they introduce an option to turn off broken font antialiasing. It’s painful to look at.

browser running in RAM

What does this mean?

End result is that aside from guests not having HW acceleration for thing like video playback, things just work like with normally installed programs. Double-click an icon, and it launches.

The same but with automatic hardware passthrough is easy with distrobox and distrobox-export. Or is it not the same?

Goodbye X11… Wait, it’s not 6.8 yet… But I think about it every update.