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.

It’s definitely more intuitive but It would drive me insane having to type that all out.

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.

I will spend an entire weekend ricing my desktop in just the right way.

Then I’ll notice that one of my main apps doesn’t adhere to the theming i’ve designed, or that <insert random condition here> will completely break my theming because <insert weird OS quirk here>, or If I change my wallpaper it will make my entire theme look like shit, or that my cool theme makes font unreadable on one app because it renders shit weird, or that I completely overlooked this one aspect of my workflow that my cool design fucks with.

Then I’ll just say fuck it and go back to using standard Gnome.

There’s an extension that lets me close and open windows with the Matrix Code Rain so I can pretend I’m cool n shit.

This keeps getting brought up, but the reality is that there is nothing special about SteamOS 3. If people want a SteamOS-like OS (Immutable, Steam/Proton integrated, Steam Big Picture as Primary interface), then it already exists. Chimera, Bazzite, probably others. The only thing Valve could realistically improve on is the installation experience.

SteamOS’s only real advantage is that it is hardware restricted. Valve is able to test against a narrow field of hardware and insure a high degree of stability because of it.

The Nvidia open-source driver situation has been improving. Supposedly Valve has been working with them on it alongside their ARM support.

You can also try your hand with the closed source drivers but ymmv.