- WPF/Silverlight does not have a language barrier (you can use VB, etc.)
- The distribution agility of Silverlight vs. XNA is off the chart. The Silverlight plugin does not require Windows (let alone the .NET framework). It's simply a browser plugin ala Flash, available for both Mac and Windows.
- XNA Click-once. Very cool for C# XNA developers, but the prospect of creating a Click-once VB hack/workaround/replacement for VB XNA apps really ups the proverbial "is this really worth it" ante.
- The basis of my 2D XNA engine (i.e. the matrix hierarchy, and a scripting engine (which I never covered, but basically it allows you to target any property of a specific data type and interpolate it over time)) this was all very cool indeed. And it all already exists, practically verbatim, in WPF*.
*While it's a bit satisfying to see I came up with the same solution that Microsoft did for scripting any object with time-based animation, it's also a very major /facepalm to see I've been reinventing the wheel for the past several months! - WPF appears to be the future of Windows development, which I'd like to stay on top of for both my career and personal interest. What's more, you can totally . You can even use . No, it's not as powerful as XNA but you have to admit; the whole ordeal is rather neato.
So someday a new blog might crop up somewhere with my WPF/Silverlight stuff on it (altho for now I'm still pretty green). I still have those game ideas tucked away waiting for implementation... someday.