I posted a majority of my feelings about WPF/E over on ZDNet but I wanted to also follow up with some stray ones here. I thought Mary Jo Foley took a good angle and she hones in on the Expression Studio, which is the biggest question mark for Microsoft.
First off, let me make sure everyone is clear – WPF/E is not a Flash killer. Flash isn’t going away, and value-adds like Flex and VoIP down the road make Flash a formidable foe for anyone getting into the cross-platform runtime business. But WPF/E isn’t trying to take Flash head on, but it does provide a needed jolt to the web video market. Flash was able to blow everyone else out of the water because a) it was everywhere and b) it was easy. WPF/E is easy to use and they’re working on the “everywhere” part. In addition, it will have some DRM functionality. Now I hate DRM as much as the next person, but with DRM sites like YouTube have a way to monetize more of their content and the big guys may be more likely to offer full shows and/or movies. WPF/E enables this and that’s a pretty powerful business use.
Expression Studio is a harder sell. From what they were able to show me, I think it’s a solid product, and they’re working with the right people. But Dreamweaver and CS2 (though they dislike that comparison) are going to be very tough nuts to crack. And the fact that it only runs on Windows means they won’t be able to make inroads into the lucrative Mac market. So then what is the endgame for Expression? To help build XAML apps? To gain some “street cred” in the design community, to take on Adobe’s tools? I’m not sure, but how that plays out over the next year is going to be very interesting.
[tags]WPF, WPF/E, Microsoft, Adobe, Expression Studio[/tags]Tweet