Nah, WCF is just as convoluted. It ships with crappy default values. I understand WHY - it's meant to limit the attack surface for things like denial of service - but they basically mean the first time you write an app using WCF it will work during testing but immediately fail as soon as you put it into production. The error messages suck.

I'll agree that taking a WCF demo app and running it in production can be a hair-pulling experience. A few years ago, I had to host a WCF service on a shared Web hosting service provider, and got an error that had me pulling my hair out. Turns out that some Web service providers have more than one host header bound to the site - so I had to do a workaround of overriding the ServiceHostFactory with code to check the number of Uri base addresses. So yes, many have some battle scars with putting WCF in production. (And sadly, some speak and write about WCF even though their production experience is either very limited or zero).

But I still don't think WCF as quite as convoluted as WPF, and I still say WCF has a more logical and intelligible framework. I definitely agree with Rick's observations on WPF.