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).
You command one or several cities and gangs of creatures (some of them beasts, some presumably sentient), lead by a person who’s armor and sword somehow makes the other creatures in his group stronger. These gangs capture other cities and fight other gangs, but they’re very civil - they let each take their turn at it.
I’d say you’re pretty lucky. Just a month and a half ago, there was a package conflict for my installed BLAS due to this. Last year there were this one, and this.
It’s not such a big deal, and it depends on the software you have installed. But it’s something one should know could happen.
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.
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.
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.