auto-generating the library?

[tve]

This is perhaps a naive question out of left field, but has there been any thought around automatically generating the guts of this library, i.e., the many calls for the many services? I recently noticed that AWS generates the libraries it maintains from metadata. For example, for ruby it's a set of JSON files you can find at https://github.com/aws/aws-sdk-core-ruby/tree/master/aws-sdk-core/apis and for node-js it's a similar set found at https://github.com/aws/aws-sdk-js/tree/master/apis
I'm just embarking on this and while it's daunting it does seem smarter than building it all out by hand...

[alimoeeny]

Huh! I didn't know about this. What parts can be generated that way?
@tve please keep us posted.

[lostghost]

In case you haven't already seen, stripe has released a generated library - https://github.com/stripe/aws-go.

[alimoeeny]

Thanks @lostghost . Very interesting. So unless we move toward a more idiomatic go and take advantage of what go provides (like returning channels on scan) and such it will be just a matter of time and goamz will be replaced by aws-go or similar libraries. Right?