News for hackers. Stuff that matters.
Re:Errplane (YC W13) launches performance monitoring and ale... by runT1ME on Monday March 18, 2013 @05:04PM (#5397119)
Did you primarily compare Scala's actors to Go's channel based concurrency, or did you also evaluate and compare Scala's monadic Future/Promise classes for building concurrent libraries?

As someone who has done a fair bit of network programming, the latter libraries/classes have resulted in some of the best code I've written and an order of magnitude productivity increase.

Re:Errplane (YC W13) launches performance monitoring and ale... by pauldix on Monday March 18, 2013 @05:20PM (#5397197)
In Scala I was using just actors and then sometimes good old java.lang.concurrent. That actually gets into one of the things I like about Go over Scala. Scala is a total mess. There are three different ways to do things, none of which seem particularly easy to use. Go has one paradigm for concurrency and it's simple to understand.