Yeah, I work for [LargeOnlineDatingService] and we're just now beginning to design around reworking our site in .NET. In, in doing so, we haven't even talked about web services.

Frankly, in our case, they're too niche. And, IMHO, that's the true problem.

Here, at [LargeOnlineDatingService], we can see a few cases where someone might want to use them. Otherwise, we'd be trying to "back into" using web services, and forcing a square peg into a round hole.

So, we're looking more at the base .NET architecture and finding that it's actually a really good step up from the previous DNA architecture.

Coming from doing J2EE for the past 2 years, it's (obviously) very similiar, especially when doing C#. ;) And, of course, MS being the King of GUIs, has made the development environment a dream vs. any combination of JBuilder/Visual Age/Webgain and Websphere/Weblogic.


Anyways, just my .02 on things.


-Jason