News for hackers. Stuff that matters.
Re:Brad Fitzpatrick on the future of Go by tptacek on Tuesday October 14, 2014 @04:50PM (#8455727)
We could not have handled the load at Microcorruption, emulating CPU state for thousands of concurrent users, using Ruby --- which remains the front-end language for the site.

We could easily have done so in Java, but we'd be in Java's concurrency model, which is much more difficult to reason about.

Re:Brad Fitzpatrick on the future of Go by kyllo on Tuesday October 14, 2014 @05:35PM (#8455971)
So, you did it in Go instead of Java, right?

I think this is exactly what people mean when they say Go is more of a replacement for Java than it is a replacement for C++: In the sense that when Ruby and Python become too slow, people normally reach for Java, but now they have Go as an alternative option, with a better concurrency model than Java's.

Re:Brad Fitzpatrick on the future of Go by tptacek on Tuesday October 14, 2014 @06:21PM (#8456144)
We never even considered writing it in Java. We wanted something with the performance characteristics of C, which is what we would have used had we not had Golang.
Re:Brad Fitzpatrick on the future of Go by seunosewa on Wednesday October 15, 2014 @05:50AM (#8457731)
Golang does not have the "performance xteristics of C"!
Re:Brad Fitzpatrick on the future of Go by tptacek on Wednesday October 15, 2014 @07:08PM (#8462371)
I must just be crazy.
Re:Brad Fitzpatrick on the future of Go by threeseed on Tuesday October 14, 2014 @06:56PM (#8456283)
There are alternatives to Java's concurrency model whilst still staying on the JVM:

http://docs.paralleluniverse.co/quasar/