|
Our philosophy is this...
If something is purely additive and something that may benefit a subset of users, the old behavior is left as the default and the new behavior is opt-in.
However, if it's something we deem as "best practice" or that we feel the vast majority of users will want to adopt, the new behavior becomes the default and the old behavior is kept available so that anyone who dislikes it can go back to the old way.
As @Merion pointed out, if we don't make something the default, few users - now and into the future - will explore and discover it. And that greatly diminishes the value of adding it in the first place. So we have to weigh each change on its own merits in this regard.
Thanks!
|