> Run as root. This is controversial, however, it is just a different philosophy. The user runs as administrator (root), apps may optionally run as user 'spot' or in containers as a "crippled root" or user 'zeus'. The practical outcome is that you never have to type "sudo" or "su" to run anything, nor get hung up with file permissions.
You have individual account for individual people. Use sudo if you need to elevate permissions - that gets fired over to your syslog server, so if you screw up you know what you did. If someone else screws up, you can see who it was and either fix it, or contact them to find out what they were trying to do (likely both)
Based on the language ("the user") and the focus on the GUI, I think this OS is designed more for single-user workstations, rather than multi-user servers. This philosophy of "root by default" is also implemented by Puppy Linux, which was created by the same person.
Single-user workstations are usually pets, and it's much easier to manage a pet when every single unit of execution is separated from other units of execution.
It's also much easier to manage each application with it's own root for everything, rather than multiple applications installed into a single root.
What's ridiculous is taking a security model designed for multiuser university mainframes in the 1970s, riddling it with 40 years of hacks to get around places where it's inconvenient, and insisting that it is the One True Way to run a personal laptop. I'm glad that some people are willing to fight dogma and be experimental.
Yeah, no thanks.