Thank you for sharing! If you remember, could you share your findings?
Hehe. I agree that the community on Lemmy gives off more mature vibes. I suppose one should at least credit them for being idealistic enough to be on Lemmy rather than Reddit.
Thank you for spreading the positivity ๐!
Thanks for pointing that out!
Bazzite also includes an entry in their documentation in which they explain how theming on Bazzite works exactly.
FWIW, by creating your own images (through BlueBuild or tooling offered by uBlue) you could bake themes directly into those folders.
However, I totally understand why you'd not feel compelled to do as such ๐ . Especially if your current distro/system works splendidly.
Sometimes, placing it to ~/.local/share/themes
works as well*.
It's a 12.5 inch device:
Linux support should be excellent.
Though, unfortunately, Star Labs' reputation regarding communicating delivery times for their products leaves a lot to desire.
Still, it's worth a look if you're not particularly in a hurry.
Would you mind elaborating?
Yup. Here's the post as found on Mastodon by the developer that works on Steam on Linux on behalf of Valve.
Uses btrfs by default but comes with no snapshots or GUI manager pre-configured for system restore
False on Fedora Atomic.
Less software availability compared to Ubuntu or Mint
Distrobox and Nix exists.
More likely to break than Ubuntu or Mint
Mint, perhaps. For Ubuntu, this was only true in the past. And only if PPAs were used sparingly. But Snaps have been a disaster for them in this case. So much so, that even Valve told Ubuntu users to use the Flatpak for Steam instead of the Snap.
Can't agree more.
I believe Flatpak initially couldn't and/or didn't want to do CLI. At some point, it offered some basic functionality; I first noticed it on Bottles. But, it's pretty dire if no variation of top
can be found as a Flatpak.
I wouldn't be surprised if most people are simply unaware that Flatpak can even do CLI. This inevitably also negatively affects its CLI ecosystem.
True~ish.
There's an important caveat though; for whatever reason,
rpm-ostree
can outright fail to upgrade (due to conflicts related to layered packages) while an issue like that is more rare on traditional Fedora anddnf
. Thankfully, I've never had a problem that I couldn't solve withrpm-ostree reset
run on a (previously) pinned deployment (throughsudo ostree admin pin <insert number>
). However, when used irresponsibly, this (i.e. layering) can outright destroy your otherwise very robust 'immutable' distro.It's easier to teach people to be cautious than to teach how they should act accordingly. Hence, uBlue's documentation tends to be more conservative in order to protect (especially newer) users from shooting themselves in the foot.