Re: I too found after some use
. Providing the OPTION hurts no-one, because people DO work differently.
It does though. It's expensive for one thing, every single option literally doubles the size of the test matrix, so adding more choices pushing up the cost of development exponentially.
For another thing, it means you have to come up with multiple ways of surfacing each new bit of functionality, made worse by the fact whichever way you chose to expose it in the "old" arrangement will be changed functionality there anyway, so you're effectively changing functionality in the old feature even though you're supposedly keeping that there for people who don't want change.
Finally, but perhaps more importantly, it's lazy. It's so easy when designing a User Interface to sidestep every difficult decision by just saying "Well we'll include both solutions and just make it optional". This is a disservice to end users, leaving them with something that just feels unfinished and clunky. As a designer you have to make the hard choices and come up with something that works. Users might complain about change at first, but, if you made good decisions, they will thank you in the long run when they adapt to the change and find themselves becoming more productive as a result. The is one of the reasons Apple products are always held in such high regard, because it's something they tend to be much stricter on than anyone else