>Someone makes a project trying to make something easier to learn (so, trying to make the world a better place)

Again, spare me the hyperbolic the "trying to make the world a better place." The principle behind my post, as given in my very first statement is that they basically failed. They are gearing people towards failure. It would have been better to just create a thin layer on top of git with slightly renamed or alias commands -- all while having "release valves" that guide you into the true, underlying community crafted toolset underneath that git has been using for years (and for very good reason). Any errors you're likely to come across while using git have been documented either by the team or in various posts around the internet. It's easy to search for these errors. If your target audience are developers who have a hard time with Git, why would you make it needlessly hard to research errors that are likely to happen (given how new this tooling is). For example: labeling rebasing as "fusing" is basically telling them: "haha, good luck googling what just went wrong!". Good luck hopping on an IRC or Slack channel and getting someone to help you. A decade of community problem solving and documentation just went out the window because the Gitless team decided to play musical semantics with commands.

>why would you take such a hostile tone towards anyone's work, ever?

Leave your ego at the door. We're talking about a toolset.

>Besides your arrogant "I'm right, you're stupid and wrong, and there's no questioning me" attitude

Please do not respond to any of my posts in this thread anymore, especially if that is the basis of this comment chain. That is a ridiculous sentiment and I'm not going to devote any effort into addressing it.

>I'm hugely sympathetic to the opinion that Git is needlessly difficult to learn and needless easy to make mistakes

I would strongly disagree about the "needlessly difficult" part, but I would also claim that the "easy to make mistakes" is demonstrably false with Git. Git makes it extremely difficult again to do something you should not be doing in the first place and then the community over the years has placed plenty of warnings when you do those questionable actions anyways; on top of giving you the ability to revert the mistake and bring your repository to a sane place with one simple command. Checking out branches with conflicting changes is just one of the simpler safety checks and roadblock that Git provides where Gitless decided to just go "Nah, you can actually do that." with seemingly no apology as to why you would ever want to allow such a thing -- other than just for the sake of convenience, but I would label it as laziness as it makes it incredibly easy to pollute your repository at that point. It doesn't even provide any kind of warning mechanism or cleanup tool for this handy "feature."

>So instead I'm trying to convey that your arrogance is unacceptable in the community in the hopes that it will not reappear.

The only thing worse than calling me arrogant is your complete, unconstructive obliviousness towards your own attitude. Not only have you still failed to say anything worthwhile or present any kind of counter to my opinion, but you're being a complete dick about it and trying to label me in a negative light for no reason. Which ends up really at the end of the day making you a troll at worst and a hypocrite at best.