Git experience is highly transferrable. Unless you have some specific use case not supported by Git, why wouldn’t you use the one where the knowledge is most likely to carry over between projects/jobs?
I am one of those weirdos who prefer the best tool for a job, not the most popular one. And Git is - for me and my projects with exactly one branch (“trunk”) and three or four other contributors, with me being the BDFL - the worst choice.
Git experience is highly transferrable. Unless you have some specific use case not supported by Git, why wouldn’t you use the one where the knowledge is most likely to carry over between projects/jobs?
I am one of those weirdos who prefer the best tool for a job, not the most popular one. And Git is - for me and my projects with exactly one branch (“trunk”) and three or four other contributors, with me being the BDFL - the worst choice.