Yes, it's fast, but it sucks at everything else ("suck" is a bit too hard, it's more that other tools are more pleasant to use).
Still,the question you pose is an interesting one. I am curious to hear from others who have ported their projects to use git? I.e. there are hundreds of programming languages, but git it is for SCM.
Is it because the investment in learning it is so high? Is it because there are multitude of hosting solutions where others are rare and few? I really wonder!
Using the toolkit directly is awkward and comes with a steep learning curve; many of the parts have sharp edges that can result in permanent loss of your work, others have deeply unintuitive purpose (e.g. the various ways to edit history).
Any productive scaled use of git requires wrapping it, whether with scripting or process or social norms or some combination of those. Only after this work is done do you end up with something it is meaningful to compare with another VCS.
Whether the ability to customize flow to your needs justifies the effort involved compared to other VCS is really something each organisation should decide for itself.
https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.w...
