> Some people have an aversion to "goto" statements, and Java annotations are even worse, they're a "comefrom" statement, where you end up executing code before or after your function based on this annotation, so it makes the code really annoying to follow.

I like this comment so much because I would have described annotations as a "comefrom" myself... but then I probably read that somewhere and forgot about it.

> Grumpyrest looks like it makes integration with spec-driven workflows quite easy.

This is interesting to me because I always thought about it the code-first-generate-documentation way, and I always wondered if/how I can derive all the meta-data from the code which, admitted, annotations make much easier because they are statically accessible.

Doing it the spec-first way is something I should definitely consider.

> A word of caution to the author; if this takes off, you will be inundated with issues and PR's, since people will use this in ways you never dreamed of. I'm experiencing that kind of onslaught in something I open-sourced for Go for REST API's.

Thank you for the warning. Do you have any advice on how to prepare for that?