News for hackers. Stuff that matters.
Re:Best practices for a new Go developer by fauigerzigerk on Wednesday September 02, 2015 @08:56AM (#10158845)
Beginners don't remain beginners forever. My yardstick for whether or not I like a particular approach is looking at old code that I have written months ago. The more quickly I can get back into it without fear of breaking things, the better the design is.

By that admittedly subjective standard, goroutines and channels have been a big success (compared to asynchronous code).

Re:Best practices for a new Go developer by danieldk on Wednesday September 02, 2015 @10:39AM (#10159484)
By that admittedly subjective standard, goroutines and channels have been a big success (compared to asynchronous code).

Well, your barrier is also very low :). Try e.g. Erlang's actor model.

Re:Best practices for a new Go developer by fauigerzigerk on Wednesday September 02, 2015 @12:00PM (#10160124)
What puts me off Erlang is its dynamic typing and lack of speed for algorithmic code. I'm just not smart enough for dynamically typed languages it seems (even though I do like some of them -- Python).