I've worked with a number of teams that use Git, and they all use it like a centralized VCS
The D in DVCS stands for distributed, not decentralized. The model is up to you, but even with a centralized one there are many benefits. Try bisecting with SVN.
except it's more awkward to set up and use than a VCS like SVN or Perforce or even CVS is.
Then you must be doing something wrong. I’ve had to handle both SVN and git repo sharing and git was a breeze compared to SVN. Not to mention starting a project on your own is as easy as `git init`.
Then they spend more time arguing about whether or not to rebase than they spend actually developing software.
Sure, the tool is to blame for people who like bikeshedding.
It's a real shame that Mercurial didn't win out. It's a superior DVCS in every way, except for not having as much mindless hype surrounding it. But I suppose in some ways that's one of its best features, too. It hasn't attracted all of the fools that Git has.
My first DVCS experience was with Mercurial, and I’m glad git won the race. The only features I missed when moving to git were `hg incoming` and `hg outgoing` and I kinda managed to implement them with aliases using fetch and log, so I’m happy now.