Should I go with WPF?
January 31, 2007 | 2:55 pmThat, was the question that I had been asking myself for the past couple of months. Sure, the screenshots rock. Sure, the features rock. But, I was percieving it as a bit “complex”. That would be put into perspective if you get a bit of my background: I first heard about .NET when Visual Studio 2005 was in Beta 2, and I first heard about VB6 when .NET 1.1 had been launched. So, I’ve had it easy, especially in the IDE side: Everything had been done for me from Day 1. Not many bugs. Even the betas of VS2005 were pretty much smooth.
But, WPF? VS support was dismal to say the least, and the UI designer (Blend) looked more like Illustrator than Visual Studio. And, the XAML code? Grids, Stacks, whatnot! It seemed like I was trying to write a device driver in Java!
But, that was, until I saw this damn cool screencast from Channel9. It’s a bit old, and the bits used are a bit old as well, but after I saw that screencast, I’m hooked on. Complex? Nope. Would you say HTML is complex?:D No Designer? Who cares! I’ll use any XML editor, and the one that comes with Visual Studio has Intellisense as well. I digg WPF. My next application(for which I’m drawing prototypes during Chemistry class, so that I’m not wasting time), is in WPF.
And, when is the Channel9 Video embed gadget coming? Or, is it coming at all?:D Let’s see if anyone from Channel9 heads here, to the blog of this Y-Lister….
P.S: HeyRobert Scoble, have you forgotten about us developers? I don’t think I’ve seen any Developer oriented videos at PodTech or ScobleShow.






