Digging in WCF

I've been digging in WCF for a while now and i like what i've found. The biggest thing is by far the shifting (both mentality and implementation) from remote objects (a la .NET Remoting) to messages (WS).
On the downside lots of WCF goodies are available only when using a few bindings (TCP and WS Duplex mostly). If you "craft" a solution who's implementation is based on these goodies then you're stuck with these bindings. And of course you're missing one of the best features of WCF (binding switching...and implicit transport optimizations, by modifying the config file).
If i'd have to go with a intranet distributed app then i think i'd go with WCF now. But for the internet i still think the .NET WS stack is a better solution ( why ?.....because the WS stack is a lot simpler than WCF).