As you proparly know, the WCF-dlls are based on the mscorlib of .NET 2.0.
It is slower indeed, but what I meant is that you do enable all the possible communication options with WCF. You just can configure it. So you aren’t limited to ‘just remoting’.

Second, I am not sure that WCF can replace .NET Remoting, because it is something else. Supporting both frameworks would probably be the way to go.

Remoting is a lot faster than WCF (google it), up to a factor 4. This is naturally extremely relevant when implementing enterprise application.

It is true that WCF percents some new features. It is more a SOA way of doing things, but is that a good thing?

I still swear to the object orientated paradigm and abstract data types. So until I am 100% sure that WCF supports the same passing of object graphs that .NET Remoting does, I will remain skeptical.

I will probably soon be on a project that uses WCF in real life. After that, I can tell you if WCF is the holy grail

I did not forget about WCF – I simply commented that the first real .NET 2.0 version of Sitecore (yeah, ok 5.2 was .NET 2.0 as well) did not support .NET Remoting.

When Sitecore comes in a .NET 3.0 version, let’s talk WCF