Problem 1: Developers unaware of the full capabilities of their DVCS system (thinking they can't do work because github is down). Solution: Education. Problem

Problem 1: Developers unaware of the full capabilities of their DVCS system (thinking they can't do work because github is down). Solution: Education. Problem 2: Lots of versions of big blobs. Solution: git clone --depth 1 remote-url Problem 3: Big commit history. Solution: git clone --depth 1 remote-url Problem 4: Bad UX. Solution: Write a better UI, or find someone to do it. Linus is not a UX guy and never will be. Also, the example workflow differences are pretty similar to the differences between the github model and the Linux contribution model. This has nothing to do with DVCS vs VCS. So, in short, there's no actual fundamental problem with DVCS. Nothing to see here. Move along.