One of the problems, for a popular tool with a long history, is how do you get from a sub-optimal UI state ‘A’ to an optimal UI state ‘B’ without the transition states being worse than the starting state ‘A’.
For example, Stack’s command line looks like this:
The commands in group 7 all provide information to the Stack user. For me, they are a bit of a mess - but would getting to something more coherent be more painful for users than that situation.