Re:An experimental, automatically generated set of AWS clien...
by nl on Monday December 15, 2014 @03:14AM
(#8751072)
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.
Re:An experimental, automatically generated set of AWS clien...
by threeseed on Monday December 15, 2014 @05:22AM
(#8751332)
> 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.
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.