After watching the video I totally agree with Danny even though I don't use the feature as demoed.
Many years ago, while I was still a business apps developer, if there is any change in the user interface, we make it a point to have an option to check / unchecked these U.I changes - with the default unchecked so existing user base may use it unchanged. Only clients that asked for the feature will have to turn it on.
The system ends up with pages of (complicated) setup screens. But if this was not done, we have hundreds of users jumping on us complaining why it's all different. And they hate any U.I changes when it affected their work flow, especially business apps dealing with front end cash collection. We've learnt our lessons and we choose the U.I setup way.
So there you have it. It's either a system that preserve old workings,etc.. but ended up with pages of setups (for U.I preference) or a system that implements the latest toolkit features without setup or with partial setup.