Can anyone add practical experience with the API spec tools. This is a new name for me.
I had a look at the websites for each of the three tools the article specifically mentions
http://raml.org/
http://swagger.io/
https://apiblueprint.org/
I get the impression that these are code generating tools built from a specification file.
I have real world experience with two tools which fit that rough description. SOAP and google app-engine end-points.
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't obviously buggy, but app engine endpoints are unpredictable and the generated code produces some serious awkwardness.
I don't want to slap a label on these tools and dismiss them off-hand.
Anyone used them 'for the win'?
I had a look at the websites for each of the three tools the article specifically mentions
I get the impression that these are code generating tools built from a specification file.I have real world experience with two tools which fit that rough description. SOAP and google app-engine end-points.
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't obviously buggy, but app engine endpoints are unpredictable and the generated code produces some serious awkwardness.
I don't want to slap a label on these tools and dismiss them off-hand.
Anyone used them 'for the win'?