Should I suggest to use version control for writing a paper with new collaborators? I will soon write a new article with new collaborators (my first paper with other people, I'm in math). For some context, I know one of them well, but I've never met the others in person.

I use Git to manage all my papers. I'm wondering if I should suggest the use of Git to them? If so, how much should I press the issue, what should I say when suggesting it?

I can use it alone and apply their changes manually, but it would be infinitely easier if everyone just used a VCS -- and not just for my own personal comfort, because Git (or any VCS) does make writing the paper easier, IMO.

The main issue is Git's learning curve. I can offer to make everything as simple as possible (set up the repository myself, help out with technical issues they might have, direct them to tutorials), but academics are busy people, and they might not want to learn a whole new system for just one paper (even though I believe that were I they, I would then use Git for everything...).



I've gotten a lot of answers that don't apply at all to my situations, so to clarify: I'm in (pure) mathematics, where all manuscripts are written in LaTeX. So 


version control using, e.g., Git, is appropriate, since LaTeX is a plain text format (and not some WYSIWYG thing), and 
it requires a little bit of technical know-how already, so it's IMO safe to assume that other collaborators are not completely tech-illiterate.
I recently was on the other side of this - I learned git to work with a collaborator on a paper (written in LaTeX). While git is fun, and it's good I learned it, I am not convinced the net time savings were that large, and I found the first steps very frustrating. I would not generally recommend you ask collaborators to learn git - but only ask if they already know it. For papers, maybe things like overleaf/etc might be better?

Giant time losses:


 Trying to figure out how to properly discard changes I made but didn't want to merge, when stash didn't seem to work right...
 Accidentally doing bad commits, etc, and trying to figure out how to move backwards.


This would obviously get easier the more you worked with it, but I found that in the first few months, there was some problem like that, and I ended up deleting everything and re-downloading - this xkcd sounds about right: https://xkcd.com/1597/

Upside:


 Fewer ugly email chains
 Made integrating small edits late in the process a lot easier - I was more willing to make tiny wording changes when it didn't require someone else to integrate it into the final draft, and that I could do it on my time.