usarid

4 ms·

1. 1.▲
   by usarid 13y ago

   Regarding tooling.. check out the video that just went up on http://raml.org (and on Youtube: http://youtu.be/5o_nExedezw )
2. 2.▲
   by usarid 13y ago

   In short, we wanted an API spec that was much more readable and efficient, showed the structure of the API more clearly, and promoted consistency and reuse. We wanted an API spec that was intuitive enough to just type out in an editor when
3. 3.▲
   by usarid 13y ago

   couldn't agree more that it ain't much without tooling -- RAML's been out for only about 24 hours, but open-source tooling is right around the corner (weeks, not months).
4. 4.▲
   by usarid 13y ago

   (disclaimer, I'm from the RAML workgroup -- nice to see you here, Jakub!) As you know, we carefully considered swagger and blueprint, before embarking on the RAML path. There's a bunch of us who are strong believers in very human-
5. 5.▲
   by usarid 13y ago

   I like to think design-first and if possible in the most minimal fashion that captures the interface, but I certainly see (and share) the appeal of writing working code. In many cases like that (including APIs that are already implemented i