News for hackers. Stuff that matters.
Re:Brad Fitzpatrick on the future of Go by socket on Tuesday October 14, 2014 @10:44PM (#8456951)
You are mistaken if you think Amazon is backed by "enterprise" Java apps from a single codebase.
Re:Brad Fitzpatrick on the future of Go by e12e on Wednesday October 15, 2014 @04:31AM (#8457602)
For what it's worth, a pristine checkout of Eucalyptus[1], that has parts written in Java, appears to be around 430k loc of java (comments and white space included).

Also, OT, didn't realize Eucalyptus had worked so much towards friendly development, and was moving towards including RiakCS as a S3 work-a-like backend[2].

[1] https://github.com/eucalyptus/eucalyptus [2] https://github.com/eucalyptus/eucalyptus/wiki/Scalable-Walru...

[edit: yes, I realize you were probably talking about Amazon the shopping cart, not Amazon the IT infrastructure provider]

Re:Brad Fitzpatrick on the future of Go by SiVal on Wednesday October 15, 2014 @02:28AM (#8457386)
I was under the impression that Amazon was primarily a collection of services written mostly in Perl. Socket, do you know?
Re:Brad Fitzpatrick on the future of Go by kyllo on Wednesday October 15, 2014 @09:57AM (#8458418)
What I've heard from a friend who's a SDE there is that because they have a Service-Oriented Architecture the individual teams can use just about whatever language they feel is best for the particular job. The other teams don't care because they're just making service calls. I'm sure that was mostly Perl in the 90s, but today it is mostly Java, because their HR strategy is basically to hoover up all the fresh CS grads, whose strongest language is almost always Java. And also because when Amazon started building their SOA, Java/XML/SOAP was all the rage.