Good-bye Windows Workflow Foundation see you in 2011
I find the investment in time to learn how to use 3.0/3.5 has been a complete waste time. So we have release 1.0 and 1.5 of WWF becoming obsolete in favor of version 2.0. These are the real release numbers on these libraries, and that is how they should have been labeled. They are not release 3.0 and 3.5.
I am not jumping on the happy happy joy joy bandwagon I have been reading about. That is- Isn’t it wonderful how big brother Microsoft is looking out for our best interest by listening to the complaints of its customers.
This takes us back to a time when you could not trust a first release of most things coming from Microsoft. This can be attributed to the complexity levels found in today’s software increasing with levels of abstraction, instead of decreasing. In order to make them decrease the software would have to be rock solid, not confusing and difficult to use. We are just throwing a new layer of confusion into the mix using these premature libraries.
I wrote this blog on the topic sometime ago. It appears we cannot blindly trust that releases from Microsoft will be around for more than 2-3 years without becoming obsolete or needing to be completely re-written.
I am having a tough time pin pointing the failure. I am leaning towards: the failure is due to a lack of industry knowledge, like when they released the Marketing Invented DNA Framework to sell the developer community a line of crap to get them to further invest in Microsoft development tools. WF has that ring to it. They are stepping into the implementation details that may be better off left to the architects developing the actual software for the given domain.
I understand that if what I am calling version 1.0 and 1.5 had never released, we would not have known what to put in the 2.0 (Microsoft’s 4.0) version of WF. The Microsoft Partner program should be better utilized for these ventures. Let them suffer a little for the big discounts they get, and stop making the development community at large suffer. That would of course mean sacrificing a few sales for the good of your customers.
How about some rebate checks for the books bought, time spent reading them, and the time spent learning the premature release of an overly complex framework that should have never been released??
I’ll be directing my team to drop Workflow from all architectures effective immediately, and to not bring it back into the mix of possibilities until the release that comes after the 4.0 release.
Blogs, Articles, Papers, and Videos mentioned above:
Windows Workflow Changes Direction
Windows Workflow Changes Direction: Write New Workflows with .NET 4.0 in Mind
PDC2008: Workflow Foundation 4
WF 4.0- the new runtime model
An introduction to Windows Communication Foundation 4.0, Windows Workflow Foundation 4.0 and Windows Server “Dublin” technologies
WF 4.0: Big Changes Ahead
WF 4.0- A First Look