The documentation doesn't do anything to convince the reader that gitless' UI is more consistent than git's.
Let's pretend I'm a newbie. All I see in the documentation are a list of commands that have pretty much 1:1 mappings in git. How is it better?
It's much more geared towards actions rather than commands.
gitless remotes look exactly the same as git remotes as far as I can tell. Why are they saner?
git init vs. git clone is a triviality, though I'll grant you that init works for both use cases
publish is just a synonym for push, and pull is what gitless seems to call merge. gitless seems to outright ignore the fetch/merge distinction. How do I fetch commits from a remote repository without merging them?
Overall the impression I get from that single web page of documentation is that gitless is a porcelain that misses the point on many things. I realize I might be completely wrong, but gitless' documentation neither answers my questions nor encourages me to try it out.
You're seeing negative comments wondering about gitless' purpose because the introduction fails to offer any motivation.
That's the thing, if you've learnt them, gitless is useless to you. I'm not interested in learning whether a branch is deleted with -d or -D or git rm branch or whichever one they used for that specific command, so gitless making them all consistent is definitely an improvement.