.. and have been for a long time. I don't remember the last time I reached for a hand-written SDK for a HTTP API. It's always some codegen affair. But out-of-the-box experience for many codegen tools is that the generated API ends up being very far in usability from what you'd write by yourself.
The API consumer should be able to adapt the binding to their needs and idioms instead of relying on behavior encoded in a pre-built SDK. The ability to do that with specific codegen tools (e.g. swagger-codegen, go-swagger) is pretty high-barrier. Oagen-emitters looks like something that addresses that gap.
Comments
.. and have been for a long time. I don't remember the last time I reached for a hand-written SDK for a HTTP API. It's always some codegen affair. But out-of-the-box experience for many codegen tools is that the generated API ends up being very far in usability from what you'd write by yourself.
The API consumer should be able to adapt the binding to their needs and idioms instead of relying on behavior encoded in a pre-built SDK. The ability to do that with specific codegen tools (e.g. swagger-codegen, go-swagger) is pretty high-barrier. Oagen-emitters looks like something that addresses that gap.