[andrewstuart]

This sort of argument is very odd. Amazon can't justify putting the resources into building a golang SDK for AWS but it appears that Stripe can. Perhaps even more strangely, someone who works at Stripe can justify doing it on their spare time, but Amazon what hasn't got the money to justify it?

Companies that provide programmable systems should be the first to provide SDK's, even for technologies not yet widely adopted. That goes for any company that provides something programmable.

Amazon appears to have no trouble at all justifying the massive development effort required for every new back end web service they build, but front end programming API access just isn't valued as much.

[nl]

Amazon appears to have no trouble at all justifying the massive development effort required for every new back end web service they build, but front end programming API access just isn't valued as much.

Honestly, is that really a surprise at all?

REST web services work well. Most languages have frameworks with excellent support for them.

Historically, the community has provided wrappers for popular APIs pretty quickly.

In the specific case of Go, it's still in early adopter territory. That means they are unlikely to have a problem using the raw APIs.

[threeseed]

> Amazon appears to have no trouble at all justifying the massive development effort required for every new back end web service they build, but front end programming API access just isn't valued as much.

Their back end services make them money. Creating a Go API does not.

Makes it hard to justify investing development resources.

[codahale]

I didn't do this in my spare time.

I did this in rough a week and a half of full-time work.