Why WPF/E Will Kill Flash
WPF/E is Microsoft’s newly introduced technology meant to compete with Adobe’s Flash . The community preview for WPF/E was released in February. In a bold statement, Microsoft released plugins for IE6, IE7, FireFox, and Macintosh’s Safari. Is this yet another latecomer technology offering that won’t quite catch on? I don’t think so.
When marketing or business people seek out software developers to solve a problem, geeks seldom consider Flash a genuine tool to solve the problem. Business people may get the idea to use Flash themselves, and in that case they seek out a different kind of person to solve their problem. Flash is most commonly wielded by people who have “Designer”, “Artist”, “Media”, or “Creative” in their titles and everyone recognizes this.
Why are there are so few “serious” business software solutions implemented in Flash? Simple: The development environment is geared toward non-coders. Creating a Flash animation is not unlike editing video or audio tracks with a little scripting available as an aside. It is an amazingly effective environment for creating animations, media presentations, and simple branching logic. But, additions like ActionScript simply wring the last usable life out of Flash as an environment for application development.
Attempts have been made to marry the worlds of Flash and “real” development languages, with good technical success but little adoption. NeoSwiff creates SWF files from C# programs and received good play in the blogosphere, but is this a ubiquitous tool in our development toolbox? Hardly. It isn’t part of the platform, after all.
Microsoft has taken the opposite approach by centering the technology around structured language. In version 1, developers will be able to script WPF/E with standard JavaScript, an improvement over ActionScript. A mini CLR will baked in to version 2, making WPF/E a genuine software development platform. This is the Flash killer part, by the way.
Including a security conscience CLR will allow support for more stodgy traditional programmers (like me) as well as the creative folks who will flock to the new development tools that will appear. IDEs will undoubtedly appear for all classes of users including the creative types. It won’t be hard to improve upon Flash MX, after all.
That is why WPF/E will kill Flash. Because enterprise and SaaS developers will be using to solve real business problems and as long as it is available, it will become a ubiquitous tool for the animators, mini game makers, and Jib Jabs out there.
Had Microsoft introduced WPF/E 2 years ago, we may not have had to endure the last year of AJAX.
Things have changed quite a bit with Flash in the last year. Take a look at the Flex Builder IDE and the Flex 2 framework. The Flex 2 framework is more enterprise ready than WPF/E and while Actionscript 3 is no match for the CLR it is more capable than the Javascript engines that WPF/E v1 will be leveraging.
Here is a good article on the limitations of WPF/E for application development:
http://www.west-wind.com/weblog/ShowPost.aspx?id=16785
I prefer the WPF/E model over the SWF model myself, but Microsoft has a lot of catching up to do, both from a technology standpoint and ubiquity of the WPF/E runtime (although of course they could always push it out as a critical update like they did with IE7)
Thanks for the link, Ken. I agree that mS has a lot of catching up to do. I am sure that we are 18 months away from seeing genuine feature parity, but when we do, I suspect that the embedded CLR will make all the difference.
I think the real point is that this new packaging of “flash-ness” will change the mindset of typical developers and we will see more button and dtagrid type applications done in WPF/E.
This is the most “incorrect” phrase of a man mind! Everything that does not interoperate with linux is useless! Because Linux is free and there are always a few people that can not pay for buggy Windows! And as IT is being more practical day by day in all countries, Windows is fading out. In 5 years Linux and Mac and windows will be equal rivals. (Almost as always Microsoft can copy everything.)