Can anyone add practical experience with the API spec tools. This is a new name for me.<p>I had a look at the websites for each of the three tools the article specifically mentions<p><pre><code>    http:&#x2F;&#x2F;raml.org&#x2F;
    http:&#x2F;&#x2F;swagger.io&#x2F;
    https:&#x2F;&#x2F;apiblueprint.org&#x2F;
</code></pre>
I get the impression that these are code generating tools built from a specification file.<p>I have real world experience with two tools which fit that rough description. SOAP and google app-engine end-points.<p>I would unambiguously describe both as awful. Really horrible experiences with both. They tie your systems to large, and difficult to understand tool sets. SOAP wasn&#x27;t obviously buggy, but app engine endpoints are unpredictable and the generated code produces some serious awkwardness.<p>I don&#x27;t want to slap a label on these tools and dismiss them off-hand.<p>Anyone used them &#x27;for the win&#x27;?