I don't really agree about the merging of information (the rest is fine). In the example, what happens if you want to sort by state or zip (assuming they are sortable)? The upgrade is really just a downgrade functionality wise in that case. This is something I find happens time and time again, an app will get redesigned and lose functionality to look simpler. It might not be the case here if it doesn't need to allow sorting, but I hate that general trend/idea.
There are better ways to have less crowded information (custom optional columns), that doesn't remove functionality. Also the more flexible a UI, imo, the better, so long as the flexibility does not increase complexity too much and it's obvious (if the setting for the columns is hidden in some obscure place, it's useless).
Merging fields for display doesn't preclude sorting by the merged fields, which may or may not be trivial depending on the UI libraries being used. But if the user wants to sort by state, it's worth finding out why. Is it so they can "simply" scroll down 50 pages to the Louisiana customers in order to print out a screenshot and fax it to the Louisiana office?
That's true, I just feel the example is a bit dangerous. It could be really good advice in one context and really bad in another.
Also sorting a table is rarely more complex than filtering the data by some property, and although I avoid UI libraries, I can't think how one could get in the way.
There are better ways to have less crowded information (custom optional columns), that doesn't remove functionality. Also the more flexible a UI, imo, the better, so long as the flexibility does not increase complexity too much and it's obvious (if the setting for the columns is hidden in some obscure place, it's useless).