No approach to technology architecture is a "silver bullet," especially with a stack spread across client and server. I always find myself returning to the "bo

No approach to technology architecture is a "silver bullet," especially with a stack spread across client and server. I always find myself returning to the "boring, old-fashioned" way of doing things (like server-side processing or relational databases) and these do indeed seem like the best choices for many applications. But I don't see how this calls client-side MVC into question, except that perhaps it's considered as a default choice too often.