rush

genuinely just a horrible take

it lacks Wayland support.

It lacks wayland support in the sense that the UI won’t run on Wayland. It can take screenshots on Wayland.

well expecting to use a tool made for X on Wayland is expecting a boat paddle to move a car.

Should be as simple as a shader on-top of Weston or sum 🤷

It’s pointless, but it’s customization.

Either way, XFCE already has plans for Wayland support

There’s elementary/pantheon tweaks for titlebar editing, other than that you just click the app’s icon on the dock again.

On the topic of void, note that they offer a glibc version too

On the startpage of the settings there’s an animation speed slider, including an option to turn them off entirely.

Well yeah, LibAdwaita is the flagship implementation of GNOME’s design guidelines.

It recommends new users to just install everything with it, instead of looking for native alternatives.

There’s actually the “Zorin-exec-guard”, which runs when you wanna use an AppImage (for integration) or windows app and tries to match the filename to a known list of either native versions of the program or native alternatives. It then prompts you if you wanna use those instead.

They’ve also released a migration tool for a future Z16 > Z17 migration and migration between Core & Pro.

Another thing, the extensions and everything needed for pro layouts is all in the repos but disabled by default. You can all enable it manually.

because obtainium gets many apps directly from F-Droid.org too, not just github

And for those downloads, it does no verification

Not on GitHub either, where signatures are often attached together with the APK.

If OSTree suits you better, that’s fine!

The A/B Partition method and OSTree are both great, but have different strengths

VanillaOS described it in their FAQ once:

Vanilla OS uses an A/B structure (ABRoot), which transacts updates atomically between two root micro partitions. The benefits of this system are the guarantee that the system is altered only when the entire transaction is successful (concept of atomicity), furthermore, the double root partition structure allows you to roll back to the previous state, directly from your boot, you will always have a home to come back to.

This structure, unlike others, is compatible with already existing distributions and does not require a complex setup and allows easy re-initialization of the system without data loss.

The 40gb total are both already reserved, and a normal user isn’t supposed to modify it so it shouldn’t fill up.

For desktop apps, Vanilla will primarily stick to Flatpaks, so Firefox will also be a Flatpak.

VanillaOS already has a custom boot menu that can be used to switch slots in case an update went wrong, so that you can go back to your older, but working system.

The partitions are also not synced.

If you install something using abroot (e.g an update) it will only be installed to the unused slot. So if you run abroot --update or use the included updater, and you’re in Slot A, it’ll modify Slot B, and vice versa.

It doesn’t sign it locally, it verifies the file you downloaded is already signed properly as it should be. This ensures the download isn’t broken but also that the app is from who they claim it is.

When you’re on A, updates go to B. When you’re on B, updates go to A.

After an update, a reboot will switch slots.

Technically, only apt exists, as per Debian. The filesystem is ext4 but with two system partitions, so that you:

• have one backup partition
• can install updates to the unused partition for seemless and atomic updates
• Be immutable whilst offering easy updates

It gets compared to NixOS because NixOS is also an immutable distribution and the package manager is equally as flexible as apx (even tho apx also allows you to use nix)

Multiple package managers outside of apt/dpkg from Debian get managed automatically using the apx tool, only if you wish to use it. Otherwise, for the desktop they promote the use of Flatpaks or AppImages.

Eh, obtainium doesn’t verify signatures, it quite literally just scrapes sources.

that’s really just two differences:

• weaker separation/sandboxing (process is granted permission to everything) (mostly bad with handy usecases)
• an alias feature for binaries contained in packages so you don’t have to run them by ID

With the maintainer having added the ability to re-clock newer cards and the upcoming NVK driver, it may be a possibility in the future.

Good to see! It really needed some reorganisation