This resource talks about git's optimization for the patching work flow, but how "modern" work flows are optimized for the forking/branching work flow. The problem is that these more "social" work flows often have a commit granularity that is not compatible with git's tools (e.g. bisect). As we shift away from the patching work flow we become more tied to the ticketing system for our code's history...and these ticketing systems are often proprietary, for-pay web-based SaaS platforms.
Towards the end it gets a little bit alarmist, but hopefully that's half the fun. G'wan and read The Evolution of Social Coding with Git and let me know what you think.