Not true.

"The Model View ViewModel (MVVM) is an architectural pattern used in software engineering that originated from Microsoft as a specialization of the Presentation Model design pattern introduced by Martin Fowler"

"Broadly speaking, the Model-View-ViewModel pattern attempts to gain both the advantages of separation of functional development provided by MVC as well as leveraging the advantages of XAML and the Windows Presentation Foundation by binding data as far back (meaning as close to the Model) as possible while using the XAML, ViewModel, and any Business Layer’s inherent data checking features to validate any incoming data. The result is that the Model and Foundation drive as much of the operations as possible, minimizing the need for “code behind,” especially in the View."

- http://en.wikipedia.org/wiki/MVVM


>To be honest I do not find that answer, which is short enough to fit in a tweet, particularly helpful. For starters MVVM has been around longer than WPF or Silverlight and MVC has been around longer than the web, at least as most of us know it. Early 70s, right? In any case it does not explain the difference between the two.