RTC jazz vs git. Should I switch from RTC to git?

Question

git

By and large, the RTC suits. Does the job though! Like almost any IBM product, rtc is huge, awkward, ugly, ugly and heavy. We don't use 90% of features.
All this leads to the fact that our developers are not particularly willing to use source control, although we understand that if properly "cooked" it can become a powerful tool that can even increase productivity.
Do you think that by switching to git, the above subjective problems will disappear?

Answer 1

Ask your developers. Let them choose their own instrument.

Answer 2

Wow! Jazz is still alive!
It certainly has a good integration of everything with everything, but if you don’t use it, and even its heaviness is an obstacle to using SCM, then it’s better to refuse it.
Work should be fun. Git encourages developers to commit frequently. It's simple and fast. It's also easier to experiment with code with Git.
And Git is mainstream. The developer will not disappear with him.
But many users of centralized SCMs have a problem understanding the distributed structure of Git.

Answer 3

Git, as mentioned above, encourages developers to experiment and commit frequently. How, why, and what it gives:
If you decide, here are some resources to help you get up to speed on Git.
courses:
pcottle.github.io/learnGitBranching
gitreal.codeschool.com/levels/1/challenges/1
cheat sheet:
www.ndpsoftware.com/git-cheatsheet.html tutorials
and articles:
git-scm.com/book/en/v2
githowto.com
marklodato.github.io/visual-git-guide/index-en.html
stackoverflow.com/questions/2530060/can-you-explai...
gitready.com/advanced/2009/03/11/easily- manage-git...
nvie.com/posts/a-successful-git-branching-model