You also have to ask the question if the "distributed" functionality is really necessary. Even if companies use git or mercurial or whatever, most have a central repository anyway. They basically offer no extra value over Subversion on that specific (but most prominent) feature in practice.
A lot of the young guys I work with don't even really know about the distributed characteristics. For them git is Bitbucket or Github. that's all they know.
They'll learn. Things like cheap branching didn't become useful to me until I had a bunch of stuff going on at once, which didn't happen until I graduated to more senior roles.
One great side effect of distributed is that even if your use case is generally centralized, you de facto have a lot of valid backup states available if something in the central repo gets borked in some destructive way.