Tout avantage à utiliser ServiceStack sur ASP.NET WebAPI - Stack Overflow

I'm planning a web API which will be used by browsers/JavaScript and Android App (open to other potential clients too). While I read there are many benefits in using ServiceStack vs WCF, I'm not sure if it is still better option now that we have ASP.NET WebAPI. I found this question where ServiceStack author compares it to WCF but says that "WebApi is different to WCF in that it encourages REST-ful API design."

So, is ServiceStack still a better option over ASP.NET WebAPI, and why?

Also, how ServiceStack fits into OWIN/Katana story?

I'm planning a web API which will be used by browsers/JavaScript and Android App (open to other potential clients too). While I read there are many benefits in using ServiceStack vs WCF, I'm not sure if it is still better option now that we have ASP.NET WebAPI. I found this question where ServiceStack author compares it to WCF but says that "WebApi is different to WCF in that it encourages REST-ful API design."

So, is ServiceStack still a better option over ASP.NET WebAPI, and why?

Also, how ServiceStack fits into OWIN/Katana story?

Source