It’s like this: The WS-* project’s attempt to re-invent RPC and
pretend that you can successfully take an object-model view of networked
applications looks increasingly fanciful, in the general case.
On the other hand,
Microsoft’s Merry Men slaved away on Indigo, worked around the horrors of XSD
and WSDL, built some pretty good Visual Studio tooling, and shipped
DCOM, the Next Generation
WCF; now it’s the
way Windows wants to be talked to over the net.
Which is why the Java ecosystem has things like
WSIT, built into JAX-WS;
you may not like Windows but everyone has to talk to it.
Thus, I find a certain irony in the recent flurry of narrative from WCF insiders on the virtues of REST, the centrality of the URI, and the advantages of using GET whenever you can. And it’s not just talk, it’s manifesting in “.NET Framework 3.5 (a.k.a. ‘Orcas’)”; those holding forth have included Don Box, Omri Gazitt, and Steve Maine (and again and especially again).
I suppose that in the Big Picture, this is a good thing; since we all need to talk to Windows, anything that reduces the cost and friction has to be a win. We should probably be prepared to excuse a little bitterness, though, among people who invested all the work interoperating with what I guess we’ll soon be calling “WCF Classic”.