Christophe has an interesting article about MVC and Flex... I've never been a huge fan of MVC - I find it to lead to over-architected applications, things with abstractions for abstractions... however, the more time I spend thinking about it, there is a certain elegance to the model.

The question often comes up about how Longhorn (and specifically Avalon) should deal with these higher level models for applications. As more teams internally start building on Longhorn they begin asking what we are doing for MVC, etc.

My default answer has been - you should layer MVC on top of the platform, not integrate it in.

I think that Swing made a mistake with requiring every developer to learn MVC to do just about anything in the model. AWT was pretty simple to use, but it seems from the little I've seen on it SWT kinda nailed it. MFC obviously had a form of model/view with their document/view architecture, and it seems that they have been trying to tease that out of the system ever since... In .NET we didn't really do MVC at all - WinForms and ASP.NET both just have a direct model, although I've seen MVC implemented on top of both.

One of the architects on Avalon has brought this question up again... should be an interesting discussion...