In this question about using WCF and/or WebAPI, there is this quote:
I was asking myself the same question until I found this WCF and ASP.NET Web API comparison page on MSDN (with my own emphasis below):
Use WCF to create reliable, secure web services that accessible over a variety of transports. Use ASP.NET Web API to create HTTP-based services that are accessible from a wide variety of clients. Use ASP.NET Web API if you are creating and designing new REST-style services. Although WCF provides some support for writing REST-style services, the support for REST in ASP.NET Web API is more complete and all future REST feature improvements will be made in ASP.NET Web API. If you have an existing WCF service and you want to expose additional REST endpoints, use WCF and the WebHttpBinding.
Paraphrased: "The support for REST in WebAPI is more complete and future improvements will be in WebAPI"
Question: How is WebAPI more "complete" and "featurefull"? What is incomplete about WCF? What's been added to WebAPI?
And conversely, with regards to REST, is there anything in WCF that isn't in WebAPI?