Hacker News Reader

There's something about WCF that rubs me the wrong way. I like coding Web Services. WCF just feels like bloat on top of web services. And traditional web services can be used cross-platform. I'm not sure WCF can. Maybe I'm just sticking with not fixing something that's not broken.

View on HN

I think the sweet spot for WCF (for us at least) is for our internal APIs. The ability to easily expose the same service over a binary TCP stream or over HTTP makes a fantastic tool when you're trying to get a lot of different systems to talk to each other.

For external or HTTP-only APIs I completely agree that it's often overkill. Frameworks like servicestack are much easier to work with in those cases.

Exactly: WCF == bloat.

Bloat in XML, bloat in configuration, bloat in object model...

Reply on news.ycombinator.com