In all seriousness, this does raise the entry bar for developers getting started in .Net. Those of us who have been doing it for a while should be able to ramp up relatively quickly, but I do believe new folks will have some serious ramp up time ahead of them.
WWF is just a basic workflow framework. Not every developer will need to use this. In fact, a lot of people won't.
Similarly, WPF will mainly be used for and by people that want a much richer smart client experience.
For your average web developer (yes, I know you can use WPF through some plug-in in the browser), it hasn't changed much, as they'd use the new web services framework, which is WCF (formerly 'Indigo')...
Roy,
You forgot WTF.
SM
absolutely, at least we have a central framework... try java (and here comes the war)
I don't agree at all, folks
The programming model behind WCF is simpler than traditional .NET's web service support (up to here I'm not mentioning Visual Studio assistance, just comparing programming models)
Try to secure a web service with the basic support. Then compare with WSE 3.0 case. Finally do the same with Indigo. In every case count the total lines of code
Of course, compare with the whole set of Java's offering (IBM, BEA, Apache, etc)
You could make the same exercise trying to get the same user experience of Win Presentation Foundation or Atlas with current WinForms&ASP.NET API's. Just compare (I accept in this case that the current offering of Macromedia, for instance, is remarkable better)
In conclusion, I don't agree: new programming models will mean less line of code, quicker development and better results