Re:Go as an alternative to Node.js for Very Fast Servers
by gtani on Saturday February 23, 2013 @12:43PM
(#5270555)
What were the specific problems you had with haskell?
Re:Go as an alternative to Node.js for Very Fast Servers
by dscrd on Wednesday February 27, 2013 @05:14AM
(#5291590)
I had several small things (laziness, poor libraries [in 2009], failing to get anyone else in the organisation even the slightest bit interested, my own lacking skills) but the overall worst problem was the feeling of the disconnect between the language and the host running my program. That is of course more or less always an issue when one uses a higher level language, but I felt Haskell was so far off that it disturbed me.
Also, the negative effect one gets after going back to one's own code after several months seemed much much worse in Haskell. Haskell code is too thick, too concise, not unlike mathematics. I find it ironic that the community, apparently, values that.
I bet others have had better experiences, but I definitely did not. Hanging around with Haskell clearly taught me many good things about program design, but I don't foresee myself wanting to ever write anything on the platform ever again.
Re:Go as an alternative to Node.js for Very Fast Servers
by papsosouid on Monday February 25, 2013 @09:45AM
(#5279149)
>Please, please, don't poison your career on focusing on a single language
My career is likely older than you, I think it'll survive the horrors of using a good language. I've been running production web sites on haskell for a year so far, and it has been great.
Go was such a huge relief after that horrible catastrophe language that seems to still continue to wreck new generations. Please, please, don't poison your career on focusing on a single language, especially one as disturbing as Haskell.