The keyword is "trying." When they intentionally disable functionality they are throwing away the userbase that depends on that functionality for the hope of ge

The keyword is "trying." When they intentionally disable functionality they are throwing away the userbase that depends on that functionality for the hope of getting a bigger userbase in return. But there's no need to be that myopic. Like I said, I don't mind if they add these features and make that the default way of doing things. I don't mind if they bury the "less broad" functionality deep in some hidden configuration that I have to get at. Just keep it around for those users, give them QA articles on how to re-enable their way of doing things, and then you can have both. There have been countless counter-examples to this "priciple", by the way: The Digg to Reddit migration being the foremost in my mind, but also the Windows Mobile to Windows Phone migration and the last Firefox redesign (that was eventually mostly rolled back or made optional again after hemorrhaging users).