I agree. I've actually have had the pleasure of using SVN, mercurial/hg, and git all for enterprise software, and you're not wrong.
I'm crossing my fingers this push towards protocols and local control (away from the cloud) gives us better collaborative solutions that surpass git.
I have a recurring problem of git polluting branches when resolving merge conflicts.
The ultimate issue is that it is designed to work a very specific way and for pros to adhere to "best practices" that may not be best for their business/user case.
Instead of evolving, it seeks to ossify itself.
my favourite part of this screenshot is the assumption that, even if the asker was able to run the git command, they would know what to substitute for "dist/<custom app branch>"