Something bothers me about all this MV<i></i>* pattern stuff. It&#x27;s the notion that there is this canonical great pattern applications should follow. There&#x27;s also a lot of &quot;we&quot; involved in this, and social posturing of &quot;best practices&quot;. Look if MVWhatever works for your particular problem, knock yourself out, but I&#x27;ve seen so many badly designed applications because they tried to hammer something into an MVC framework without considering if any of that actually made sense for what their application does. And if you suggest that all this scaffolding is just hiding a more elegant design, you&#x27;re going against &quot;best practices&quot; (despite the fact that most of these &quot;best practices&quot; arise from opinionated bloggers.)<p>I feel like MVVM is generally solving the wrong problem though. Ok, so MVC tends to get nasty because people shove all the logic into the controller, the model ends up being a crappy interface to the database, and views do too much. But maybe that just means that MVC is a bad fit for what you&#x27;re doing. It doesn&#x27;t mean &quot;we&quot; need the &quot;next&quot; MVC, it means you have to do the hard work of actually designing what your application does without training wheels.