4·
2 months agoNo one mentioned it yet, but there’s also AppManager.
- 0 Posts
- 5 Comments
Joined 2 months ago
Cake day: April 15th, 2026
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
I wonder if they’ll one day just alias a bunch of stuff, kinda like what Ubuntu has done with forcing Snap down people’s throats. So, like:
sudo dnf install bottlesactually doingflatpak install bottles- OR, e.g.,
sudo dnf install tldractually doingbrew install tldr - etc…
I don’t think it’s necessarily bad as long as it’s very transparent on what it actually does (and why). And…, offers choice where applicable*.
Or…, like, introduce a new package manager that basically functions as a front-end. Would that ((and/)or the earlier alias-thing) be worse than sticking to the development of a single package manager until it does all (à la Snap)?
no layering
I foresee a future in which (so-called) sysexts will be used heavily to address the resulting gaping hole. Unfortunately, it’s not perfect either…
Though, I have to say that I find it quite hilarious to see how many alternative package managers are required to replace traditional package managers.
If I may, I’d rather prefer a translation layer like Wine, but for Android. Thankfully, it’s in the works. Soon™.
I do expect that Waydroid’s stocks will increase tremendously as Valve’s Lepton is based on it.
As for your query, it depends mostly on your sensibilities:
- Waydroid is lighter and is ever so slightly better integrated.
- VB offers superior sandboxing (and thus improved security).
FWIW, I’ve had better experiences with Waydroid, but your mileage may vary.
You’re indeed describing workflows that suit servers better. Be it “immutable”(/atomic) or not.
But, atomicity (i.e., updates either occur as a whole or simply don’t at all) have been used on our phones (source) for quite a while now. And we do all kinds of things on our phones.
Similarly, we might borrow other concepts for reliability: like e.g. making part of the root filesystem read-only at runtime. On Fedora Atomic (and its derivatives; OP’s Bluefin being one of them), this basically only applies to
/usr. This is the extent of its immutability. Most of the remaining root folder is symlinked to/var(source). Which, together with/etc, continues to be mutable. Thus, enabling it to become perfectly suitable for desktop workflows. Like, literally; there’s very little you actually can’t do on these. The main difference being how. Hence, it’s more of a paradigm shift if anything.Rant on the naming scheme
Unfortunately, the name “immutable distro” doesn’t do a great job at conveying the nuance described above. Heck, while atomic distro is definitely more descriptive, I don’t think it helps to group/categorize these distros under one name beyond contrasting it to the traditional model. Simply, because the guts of these distros tend to differ a lot compared to traditional distros. I’m afraid that this will inevitably lead to a shift in how these convos will go: Instead of peeps making all kinds of assumptions because “immutability”, they might make all kinds of assumptions based on their experiences with the popular kids; i.e. Fedora Atomic and NixOS.