Upstream images vs bazzite: https://github.com/ublue-os/countme/blob/main/growth_upstream_with_bazzite.svg
My prediction: bazzite may have more installs than Fedora KDE by the end of the year.
Upstream images vs bazzite: https://github.com/ublue-os/countme/blob/main/growth_upstream_with_bazzite.svg
My prediction: bazzite may have more installs than Fedora KDE by the end of the year.
It’s a distro that is intended to play Steam games well. Terrible if you like tinkering or hate flat pack software. Less than an ideal development environment
It’s great for tinkering. It’s just done differently than you’re used to.
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.
You’re AFAIK correct on the bold part. But definitely not on the strike-through part. You’re probably only limited by your creativity and the effort you’re willing to put into it:
its great for dev. It encourages you to use distroboxes to isolate your dev environments from each other and the host system, or even better use devcontainers for reproducible dev environments
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.
Fair point, I’ve struggled with VSCode as well. I started looking into using a local container with VSCode’s remote dev add-ons (the ones you use for sshing into a remote machine but in this case it would just be a local container), and then installing all language servers and tooling inside the container. Do you have any experience with that?