Palacegalleryratio [he/him]

I would suggest the support this has from valve that means it works great out the box does indeed make it novel.

It will move the needle far more than like 2 hobbyists flashing niche hardware. Nobody cares about that because it’s so small scale. Nobody will put in the support for that user base. Conversely the valve frame is going to be a mass market product that will be in the hands of loads of people, so issues and problems will get fixed, software will be optimised and if the install base is large enough it will be targeted with new software and features.

That’s the novelty. It’s likely going to change things.

To be fair I wouldn’t buy one of those to run Linux, and it’s not a extremely hard to see why the average consumer wouldn’t want to buy this to run Linux either:

OpenSuse is a left field choice. Nothing wrong with it - just not a typical first distro. Hope you have a great time with it! I recommend using it for a solid month then working on a windows pc for a day - you’ll be blown away by how asinine windows is once you’ve got used to Linux.

Care to elaborate?

Tails is a pretty cool thing to have around.

The Swiss German layout looks fairly reasonable in a vacuum. The ä key having 5 letter options on it is pretty wild though. The Swiss French layout is maybe better than standard French too - it’s certainly got more sensible punctuation.

Mandriva Linux, then RHEL, the Debian and fedora.

I can’t speak for Krita - I’ve not used it. But as someone who has designed a lot of software I agree with you fully here. Making software intuitive is the hardest and also most important part of my job. When I test with users the first time it soon becomes clear how stuff that me and my team thought made sense is totally opaque to the end users or just doesn’t fit into the real world workflow. It’s all well and good expecting users to learn the software - there has to be an element of that - but if you force thought, cause confusion or waste time every time you do that you add friction to the product. That friction ruins the users experience of the product and can ruin productivity.

There is a balance to be made, complexity where it allows for power is fine, if you have dedicated frequent users. E.g. my favourite editor is Vim - very complicated and (initially) opaque but also extremely powerful and logical once you know it. But complexity that adds no power or complexity in software where you don’t expect users to be using the software frequently enough to be expert in it is not ok.

My advice would be look up The Missing Semester it’s a free online MIT course on how to use the terminal and it will govern you a better understanding of how to use it and Linux more generally. Really helpful to find your way around and give you an intuitive sense of what you’re trying to achieve.

Then beyond that installing arch is easy with archinstall but it’s probably more helpful to learn about the components of desktop Linux and what they do so that you actually know what you’re doing.