News for hackers. Stuff that matters.
Re:An experimental, automatically generated set of AWS clien... by tgeek on Sunday December 14, 2014 @11:35PM (#8750682)
there are languages inside of Amazon that are first class citizens (java & ruby mostly, node.js more now). Go is too new, moving too fast, and hasn't seen the same kind of adoption yet to warrant an SDK.(despite what the folks here might think..)
Re:An experimental, automatically generated set of AWS clien... by andrewstuart on Sunday December 14, 2014 @11:50PM (#8750713)
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.

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.

Re:An experimental, automatically generated set of AWS clien... by codahale on Monday December 15, 2014 @07:20PM (#8755288)
I didn't do this in my spare time.

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

Re:An experimental, automatically generated set of AWS clien... by andrewstuart on Sunday December 14, 2014 @11:44PM (#8750698)
Not widely enough adopted, and yet Docker is built with it. So golang ultimately is a technology that Amazon has bet the farm on.
Re:An experimental, automatically generated set of AWS clien... by sciurus on Monday December 15, 2014 @12:53PM (#8753238)
For the downvoters, I assume this is a reference to the Amazon EC2 Container Service.

http://aws.amazon.com/ecs/