Go vs Haskell/Erlang has a similar showing in TechEmpower's Web Framework Benchmarks Many servers solve the c10k problem (not that it is an issue for many user

Go vs Haskell/Erlang has a similar showing in TechEmpower's Web Framework Benchmarks Many servers solve the c10k problem (not that it is an issue for many users anyway), but it always seemed as much interesting to me how your code is structured with a highly concurrent server. E.g. Yesod and Snap (via WAI) allow you to stream the request and response with conduit (and enumerator) and build nice and composable pipelines. Play 2 is also moving in that direction with their iteratee implementation: http://www.playframework.com/documentation/2.1.1/Iteratees http://www.playframework.com/documentation/2.1.1/Iteratees Iteratee/pipe-based processing would never be possible in Go, since it does not offer parametric polymorphism and typeclasses. Sure, you could write transformations to take and produce interface{}s, but it will give you as much type safety as a dynamic languages and type switches in every function.