title: Thrift as a Public API replacement for REST?
body: <p>I started creating a API for a new site I'm working on.</p>
  
  <p>I originally wanted to make it an normal REST API but I keep thinking about how cool thrift would be with the ability to compile multiple client libraries in one batch.</p>
  
  <p>Is Thrift a viable option for a public API ,sockets and all, or should I stick with REST? </p>
  
  <p>And if REST what would the best approach for creating multiple client libraries or would I just have to get down and dirty and actually write them?</p>
  
  <p>Else if Thrift, would I compile the libraries and just offer download links or simple give the developers the .thrift file to generate their own library ?</p>
  
  <p><strong>Note: It's still a small site so I would create the Thrift Specification file just for the API.</strong></p>