<ol>
<li><p>We currently just utilize soap webservices for all our communication but have been thinking about moving to WCF instead. What are the benefits of using it over an asmx service?</p></li>
<li><p>If we do go with a WCF service, can other languages still communicate with it? SOAP is standardized and all languages can interact with it.</p></li>
<li><p>Are there any really good examples of how to get started with WCF that show the benefits of it over soap?</p></li>
</ol>

<p><strong>EDIT</strong></p>

<ul>
<li>I just found <a href="https://stackoverflow.com/questions/216931/what-is-the-difference-between-an-aspnet-web-method-and-a-wcf-service">this</a> question which is quite helpful.</li>
<li>The <a href="http://msdn.microsoft.com/en-us/library/ms734712.aspx" rel="nofollow noreferrer">Getting Started Tutorial</a> is great.</li>
</ul>

There's a bit of a learning curve with WCF, but once you learn it it's no harder to implement than an asmx web services. One advantage is you can easily switch protocols and serialization from binary remoting all the way to
web protocols
. It's also easy to host either in IIS or out.
Other languages can communicate with the web protocols. Binary, not so much...
I just dug into the
Getting Started Tutorial
. It does a good job of showing the relative ease-of-use. From there, take a look at
Hosting
and more detailed
Features
.