Nice example for the evolvability aspect. "you need to never version your API" is definitely a motivator, but you can break it for sure! :)

The only Swagger specific complaint in that list is lack of hypermedia support — that's a known issue and solved in Swagger (OpenAPI) 3.0.

Hate posts which imply a framework is broken and useless. Present it instead as suggestions on how swagger could be improved or make a PR

Didn't get the point about Swagger? All comes down to 'people don't understand REST & use a tool wrong'. Applies to every tool, doesn't it?

I like to think of the author's points as tradeoffs rather than problems. You give up evolvability with strict schemas and URLs.

Tolerant deserialization is one thing protocol buffers do well (and the tools can deserialize from JSON too - developers.google.com/protoc… )

Actually applies to many other documentation/validation formats