Giving it a try can only prove the presence of fragility, not its absence :-)
Generally, people are very reluctant to criticize "hip" tools like e.g. Clojure, Haskell, Google Go, Git or its accessories. So, when 3 out of 4 people say they had problems with it, to me it weighs very heavily on the negative side.
However, that's no reason to dismiss all version control.
Also Subversion no longer stores it's data in a database so Linus's objection in this article has been resolved.
Finally, Linus's needs are pretty unique in the world. Linus isn't satisfied with Subversion for the same reasons it might work perfectly well for you.
He says SVN is better, but is more fragile (which for source control, I interpret as being worse):
SVN fixes (supposedly) those "implementation
suckiness" issues. ...
I think it's also a much more fragile setup and
there's apparently been people who lost their
entire database to corruption
Even if SVN = CVS, clearly Tarballs > SVN, according to him. His actual quote was Tarballs >> CVS. I can dig it up if you can't.If you find that personally offensive, so be it.
CVS's database is just RCS files, plus a little. Nice and easy to restore if Bad Things start to occur.
Also, if you could provide some real details on the 'complexity and awkwardness', I could share my experience which could be helpful.