Good to know regarding the (non) stutters! Is there a mechanism to reconnect applications to the compositor after a crash so that they’d survive? (or at least a plan to make such a mechanism?)
Good to know regarding the (non) stutters! Is there a mechanism to reconnect applications to the compositor after a crash so that they’d survive? (or at least a plan to make such a mechanism?)
Haven’t they started working on Cosmic instead of using Gnome and gtk because Gnome devs restricted theming? It sounds weird that they’d be able to import their themes to gtk apps, when it was the trigger for their move in the first place.
Looks very nice, hopefully they’d fix the stutters visible in the tiling example before the final version. Also, I wonder if they also keep applications alive in case of compositor crash, like KDE would in Plasma 6 (but Gnome does not yet, AFAIK).
Vizia looks really nice, but the book only covers a counter example… Sadly, this is the state of most Rust GUI libraries at the moment…
I’ve installed Arch, Arcos and Manjaro (from the Arch based distros). Manjaro and Arcos are faster and easier to install and setup compared to Arch. Manjaro has nice GUI to select kernel, GPU drivers and install software (and does not automatically move you to the newest kernel, as opposed to Arch or Arcos). They had fucked up (I think 3 times) with renewing their SSL certificate, and for a short while their ISOs were unverifiable (not that big of an issue if you ask me). Since they delay their packages’ updates, running them in testing for a few months for extra stability, installing from AUR is bound to break.
I’ve installed Manjaro on 3 computers, and worked with it extensively for about 3 years. It’s a decent distro that doesn’t deserve all the hate it gets.
AFAIK, Opensuse Tumbleweed doesn’t offer the LTS kernel… At least I haven’t found any documentation on it. Could have been great.
How long have you been using it, and on how many computers?
From the Arch wiki:
Before upgrading, users are expected to visit the Arch Linux home page to check the latest news, or alternatively subscribe to the RSS feed or the arch-announce mailing list. When updates require out-of-the-ordinary user intervention (more than what can be handled simply by following the instructions given by pacman), an appropriate news post will be made.
Before upgrading fundamental software (such as the kernel, xorg, systemd, or glibc) to a new version, look over the appropriate forum to see if there have been any reported problems.
Users must equally be aware that upgrading packages can raise unexpected problems that could need immediate intervention; therefore, it is discouraged to upgrade a stable system shortly before it is required for carrying out an important task. Instead, wait to upgrade until there is enough time available to resolve any post-upgrade issues.
So unless Endeavour devs are doing anything special to make sure you can safely upgrade without checking the Arch news (and AFAIK, they don’t, like most Arch based distros), you should probably check it. Of course it’s a matter of chance if your system is the one that gets hit by some bug or conflict, YMMV, but eventually you’d hit a snag if you ignore Arch’s devs advice.
Does Opensuse Tumbleweed offer that option?
He specifically asked for a minimal distro, that was why I brought it up.
Arch distros still require you to read the release notes before updating. It’s not a hassle free affair, and those who don’t do it are bound to break their system once in a while.
I’d avoid Arch or Arch based distros if you don’t want to always tinker with the system to keep it running.
I think Fedora best fits your needs.
Just keep in mind that rolling releases are by definition not as stable as non-rolling. For example, Kernel 6.4 has introduced an interrupt storm for some motherboards with buggy implementation of TPM interrupts, and it’d get fixed only in 6.5…
Not very minimal with regards to disk usage, though… It comes with lots of (to me) unnecessary bloat.
He wanted something stable… Arch based systems require you to read the release notes each time you upgrade to make sure there’s nothing special you must do. Those who are unaware of this requirement often end up with broken systems. Also I wouldn’t call Arch based systems without GUI configuration tools not being too complex… Arch is for those who like to tinker, edit lots of config text files and read man pages and wiki entries.
Personally, I like Arch Arcos and even Manjaro (Probably EOS as well, but it doesn’t play well with Ventoy) - but I wouldn’t recommend it to someone who just wants things to work out of the box with minimal tinkering and not require special attention when updating.
What GUI framework did you end up using in C++? Qt?
Thanks for that, it looks much nicer than Latex!