That is, you admit that most aur users delegate that function to other eyes instead of auditing the external code they are installing. A user repository outside of the official distribution repository is not a secure means of installing packages on the system, which may have root access to the system and the source code may change with each package update. Do you think that every time there is an update to a package that is not widely used, others will audit the source code for you? For that reason I stopped using Aur and by extension Arch, as their software catalog outside of aur is small.
Any major Linux distribution has a system for building packages, it's not something special to Arch. In fact, Arch's great advantage of the aur repository actually becomes a disadvantage by introducing instability and insecurity into your system when you add programs from that repository. It's amazing that people criticize Windows security with .exe's and then install packages from external repositories with the security of "trust in the repository". How can you trust code with root access to the system just because it's in the aur repository? That's the main question I would ask Arch users.
Most of the time it is achieved with the phrase: "I use Arch, btw". 😉
SUSE has its line of business in servers and cloud computing. Opensuse has desktop users as its main asset. Not wanting the company's name to appear on the distribution is because the typical users of the two are increasingly different, as well as suspecting that Leap will not continue as SLE's 1:1 solution.
Suse's decision not to have its name on the distribution means that it will be increasingly distanced from the community distribution, which is primarily run by Suse employees, so it is the company's decisions that will shape the future of the distribution.
A company's decisions are based on the benefits of its line of business, not on the benefits of the community outside its customers. This is a statement of intent that in my opinion breaks the relationship of trust between company-community.
It is time to look for another distribution, the chameleon has focused on its profits rather than on the benefits for the community.
You can install Firefox from Mozilla's own repository. It is a luxury to have in Debian a Mozilla repository to install Firefox.
If you want full system control and a rolling distribution with a good security setup, stay with openSUSE Tumbleweed. Immutable distributions like SilverBlue, Aeon,...are not recommended for everyone, only for those who don't want to administer their system and who have good hardware and a good internet connection.
Great news, but I would put more effort into making Anaconda a faster and more intuitive installer.
If you want to learn about Arch, I recommend you to use ArcoLinux, a distribution that uses the direct Arch repositories (unlike Manjaro) and serves to acquire knowledge about Arch.
The main difference between Arch and Tumbleweed, apart from the package type, is the update system. Tumbleweed does it through snapshots, which allows you to use the openQA automatic test to test the snapshot before sending it to the community. Arch upgrades on a package-by-package basis, regardless of the other packages that are part of the system.
I am 100% happy. I use a rolling distro, secure (firewall+apparmor), stable (snapshots tested through openQA) and easily revert to a previous snapshot (snapper). Yes, I am using openSUSE Tumbleweed and in my opinion there is no rolling distro that offers all these features.
The only AMD (A10-7700K) that has given me problems with wayland uses by default the old radeon driver. I switched to the amdgpu driver and everything was solved.