title: is this bad design? MVVM pattern w/ many commands on single class
body: <p>There are two common command implementations I've seen by Microsoft. One, given by <a href="http://msdn.microsoft.com/en-us/magazine/dd419663.aspx" rel="nofollow">Josh Smith here</a>, 
  places commands onto viewmodel classes. Another, given by <a href="http://msdn.microsoft.com/en-us/magazine/ff798279.aspx" rel="nofollow">Robert McCarter here</a>, makes commands accessible via a static class (so we can data-bind to them with x:Static). McCarter's approach relies more on the use of singletons and static calls than I want to take chances with, so currently I've chosen to use Josh Smith's approach. However, my "main" viewmodel has blown up in size with at least 30 commands now, as I have a Ribbon control in the main window.  Is this a sign of bad design i.e. a lack of separation of concerns? or is this common for MVVM apps? It just seems like a lot of responsibility for a single viewmodel.</p>