Everyday hassles in Go
I couldn't agree more with this article.<p>I did some Go a year ago and liked it. Then coming back to it a year later after having done some functional programming in Clojure, it's not just the lack of generics that disrupt my flow but also having to think about all sorts of imperative programming details like naming and creating variables and scope placements in cases that would otherwise be unnecessary in a functional language.<p>I feel like I have been tainted by functional programming, and now Go feel like a joyless programming language which inevitably affect productivity.<p>I am looking for a replacement programming language to solve small problems for which Python/Ruby would have traditionally been used, good file system, stream and networking APIs, but concurrency as a first class citizen, garbage collected, fast startup time. Doesn't need to be good at long running programs, but it would be great if it can evolve to play a  repeat role in a large system/process without the hassles of having to duplicate every written line of code into tests to prevent small changes from breaking things.<p>I am considering giving Haskell a try, but wondering if it might be overkill.<p>Any suggestions?