Pablo is one the most senior people on the WPF team and has been a key decision maker in deciding what scenarios WPF would address. http://www.fernicola.org/loquitor/index.php?/archives/19-When-to-use-WPF-and-when-to-use-other-technologies.html...

I was going to post something about the various levels you can use in WPF for graphics, but Pablo Fernicola beat me to it: http://www.fernicola.org/loquitor/index.php?/archives/17-WPF-Pick-Your-API-Abstraction.html

Great post on a discussion thread off Joel On Software. Lutz pointed it out...hilarious: http://discuss.joelonsoftware.com/default.asp?joel.3.219431.12 I happen to love frameworks, but I understand the sentiment in the posting.

CollectionView is a very interesting construct. After including it in my ViewModel I meant to quickly blog about the usage...but when I started thinking about it and reading a bit more about it, it becomes even more interesting. Lots of good blogging...

I've had several questions about when and why to use M-V-VM versus other approaches. The obvious purpose is abstraction of the View, reducing the amount of business logic or glue code stuck in code-behind. All tasty goodness abstractly, but here's another...