Will it run on Linux? (I mean the editor, not the games it produces.)
thingsiplay
I know how subcommands work. But that is not the point I am making. Having two dashes in front of it or not like pacman remove or pacman --remove does not change how the command operates. It is literally having two dashes or not and therefore is not an issue.
I don't think it would make ANY difference if the option was named git --pull instead git pull (you don't have to use the single uppercase). That is NOT the same semantic difference between and , because it (the pull example) operates the same as before. The only difference are the two dashes. I don't see how this creates confusion or learning difficulties.
But its just a matter of 2 dashes. It shouldn't be a problem.
I don't get why that is a problem. It's just an option name with 2 dashes in front. In fact, that is the "correct" way of handling options, as in standard option processing in GNU / Linux. I personally dislike options without dash, but on the other hand it does not bother me enough to be bothered by it. pacman --remove is almost identical to pacman remove, so I don't know why that is a "problem".
You can use long option names instead too, as each capital letter mode has a long option name, such as -R --remove and -S --sync.
-S stands for "sync". You are syncing to the online database.
I hate that too. 7z does that and its horrible.
I don't think there is some exceptional good CLI interfaces. If anything, you either notice the interface is bad or unconventional or it is cluttered, because it has lots of functionality. It also depends if it "should" fit into the Linux eco system (similar commandline system and logic) or is this tool used for any operating system. I have my own scripts as wrapper for some tools, so they are excluded from discussions here. Note I think the discussion is about commandline interfaces that operate non interactive (in other words no "live" TUIs or interactive editors), so no Vim or htop.
Tools like yt-dlp or awk or find or git are complex and overloaded with functionality, because it offers so much and has to offer all of that. Or the command works different, because of its nature of calling another command like parallel. Then there are commandlines that just deviates from the standard and bugs me a lot. One of the worst offenders to me is 7z from package extra/7zip in the Arch repositories. But it is not a standard GNU tool, therefore it does its own thing.
So in the end, I do not think there is an exceptional good CLI, only bad or complicated ones. As long as it follows Linux standards its good to go. Often the best Rust CLI tools have pretty good ones that could be listened as standouts, but none specific in particular.
There was outlier in GNOME outperforming KDE by a large amount too.
Edit: Okay, maybe not that large. I agree with you, that the outlier they had (included twice even) has a huge impact. But it is some real game and with real settings and configuration. So making an exempt just because you don't like the results would be faking the result. They just should have included a result without the outlier, just for comparison.
I was under the impression that the desktop environment (especially GNOME vs KDE) performs about the same in gaming or graphics in general. Some of the results are pretty shocking to me how much they can differ.

I know, but with the last version they did not support Linux anymore. The version before that was supported on Linux. So its unclear at the moment if the next version will do.