Disagree with a bit in the article but particularly unpalatable to me is the idea that Git should be more than it is (e.g. PR support, web UI). Seemingly obscur

Disagree with a bit in the article but particularly unpalatable to me is the idea that Git should be more than it is (e.g. PR support, web UI). Seemingly obscured in this idea is lock-in; if I don't like Git with email patch workflow, I can use Git with GitHub. If I don't like that, I can use Git with Forgejo. Good luck moving to more suitable tooling (because what is suitable often shifts over time) when you are stuck with the inertia of your entire VCS stack being one thing. Semi related: I was at an org recently who wouldn't migrate to Git because they didn't like the Git code review equivalent in Visual Studio, compared to how TFS code review looked in VS. That was seemingly the only possible way to review code - in VS.