I ran Arch for years, but I eventually realized I only really enjoyed Arch from a conceptual point of view.
The big plus for me is stability. I had a few major problems pop up after an update, and while I was able to fix them easily enough, It was still annoying that I had to do it. Fedora is nice and stable while not being too far behind.
The loss of the AUR wasn't that annoying because Fedora has the advantage of being one of the main OS's. A lot of developers treat it as a default
SteamOS-like distributions probably aren't for you right now. nvidia has massively improved over the year but it's still not on par with AMD.
Using an immutable distro (which Steam OS and its kind are) is just going to complicate things. Your easiest bet is using a distro that will install the correct drivers at install, like pop_os or mint.
You build phones, watches, tvs, washers, dryers, fridges? Why use separate hardware and software? That's just expensive. Just build a common platform that can be easily modified for everything and take advantage of production scale to reduce costs everywhere.
Slap in all those smart phone features too because why the fuck not. It's cheap, someone might be convinced to buy it because of it, and few people will avoid it because you can use your phone. Bonus points! We can collect use information.
Everyone wins! Except the customer. Because fuck them.
As long as you're cool being a bit more restricted in multiplayer games (a lot work great! But some developers are blocking linux), and you're okay with AMD (nvidia is improving though), gaming is basically on par with Windows at this point.
In some cases it's even better. I have a few games that require weird tricks to get it to work under Windows, but work fine in proton. Even Elden Ring at launch ran better on linux because it didn't have the micro-stutter issue.
I say "easily" because it wouldn't require a major effort on the scale of coreutils. It could just be a series of fancy automation scripts. It'll take effort, but not the most intense of exercises.
I made a handful of them at an old job because we had a few specific tasks that we would regularly do, but not enough to commit it to memory. I just spent an afternoon here and there slapping together python scripts with just the options we would need and tossed it into /bin
The great thing about the core philosophy of unix is that you could easily do what you suggest and maintain compatibility with applications that rely on the traditional coreutils (Which is the major reason why no one will really suggest changing the traditional syntax. It'll break way too much.).
Just build a series of applications that actively translates your "less ambiguous" commands into traditional syntax. I've done it for a number of things where the syntax is long and hard to remember.
In fact I think a "nuutilus" would actually be fairly well received for distributions that are more new user focused and a pretty worthwhile endeavor.
The "Story Points = Hours" hits so goddamn hard. Like, tell me you don't fucking understand scrum without telling me you don't understand scrum.
We had a nice, effective production process on my team until a middle manager assigned to communicate with us started in with the whole "We can't spare this many points" bullshit.
My criticism is that it largely ignores the primary advantage of Fediverse services (Decentralizing services that are designed to operate Centrally), while mostly explaining what I've always considered to be the most pointless feature (Cross Service posting).
It's a mildly neat feature if you want to centralize your entire social profile under one account (which is my security nightmare but you do you), but its not really fundamental to using federated services and its implementation can be inconsistent and confusing.
Maybe have a bunch of "Lemmy" (or whatever) nodes arranged in a circle, the same color, with the same icon, and connected to each other through the middle of the circle (not connecting to the "fediverse", although I guess you could have a transparent "Lemmy" super imposed over it) Then have the users connected to each node. Or something...I'm on a bench and just broadly visualizing it.
The next trick is explaining the fault of centralized services in a graph.
Can you elaborate on "discoverability"? Finding individual subject wikis has never been a particular problem for me. Even ones that don't use Fandom, provided they are at least active. Just googling "
<insert subject>
wikia" (I know. I can't let it go) always gets me what I need.
Can't say I see an advantage to universal accounts (I see more disadvantages), but if that's the big selling point and people really want it. I'm not opposed to having it, i've just always treated it as a mild novelty I never use.
As for decentralization, it has already been solved by MediaWiki. Which is GPL and (can be) self-hosted.
The ability to self-host your own FOSS wiki already exists and has for over two decades. It's called MediaWiki.
You could have federated accounts I guess but do editors on the Doctor Who wiki really need the ability to see posts on Mastadon or edit pages on the That 70's Wiki?
I ran Arch for years, but I eventually realized I only really enjoyed Arch from a conceptual point of view.
The big plus for me is stability. I had a few major problems pop up after an update, and while I was able to fix them easily enough, It was still annoying that I had to do it. Fedora is nice and stable while not being too far behind.
The loss of the AUR wasn't that annoying because Fedora has the advantage of being one of the main OS's. A lot of developers treat it as a default