Haskell is too academic. Go suffers from dreadful interoperability with other languages, even C.
Poll: Haskell or Go?
31–35 of 35 posts
Re: Poll: Haskell or Go?
#32Earlier quoted context omitted.
> Plus Go has easy concurrency via message passing, which is nice to have these days. Indeed. I voted Go because learning it made writing concurrent software FUN! (As it should be)
Haskell has easy message passing as well. You can plop "forkIO" in front of any IO operation to make it concurrent
Not the same thing really.
Re: Poll: Haskell or Go?
#33Would ya'll be willing to give feedback on a similar thing I'm struggling with? I've been contemplating this same question a lot of the past few months. As many readers point out, the type of application you're writing weighs heavily on what language and tools you should use. The application I'm writing is a persistent world server for a game. The world server will need to be composed of multiple servers cooperating.…
This might be of interest: http://blog.labix.org/2010/12/10/integrating-go-with-c-the-z...
Re: Poll: Haskell or Go?
#34Would ya'll be willing to give feedback on a similar thing I'm struggling with? I've been contemplating this same question a lot of the past few months. As many readers point out, the type of application you're writing weighs heavily on what language and tools you should use. The application I'm writing is a persistent world server for a game. The world server will need to be composed of multiple servers cooperating.…
This might be of interest: http://blog.labix.org/2010/12/10/integrating-go-with-c-the-z...
Thank you! This is very relevant to my interests.
Re: Poll: Haskell or Go?
#35Depends a lot on the need. Haskell has lots of fundamental weaknesses when it comes to long-running real world programs, laziness being the most obvious one.
Unless you have a space leak, how is laziness a weakness there?
I've had issues with lazy IO that caused awkward behaviour. Identifying the root cause was not trivial, and altogether, laziness gave me no benefit and caused me lots of harm. This is the most important point here: when laziness is useful very rarely but causes non-trivial trouble often, why on earth have it on by default?
I'm sorry that I cannot remember the specifics of my problems, this project was done years ago.