Re: [Haskell-cafe] Haskell not ready for Foo [was: Re: Hypothetical Haskell job in New York]

Haskell's networking support is very rudimentary. Erlang's is quite sophisticated. For network intensive applications, especially those requiring messaging, fault-tolerance, distribution, and so forth, there's no doubt that Erlang is a more productive choice. Not because of the language, per se, but because of all the stuff that is packaged with it, or available for it. Regards, John On Jan 8, 2009, at 4:10 AM, Achim Schneider wrote:

Manlio Perillo wrote:

...

Unfortunately Haskell is not yet ready for this task.

Could you -- or someone else -- please elaborate on this?

I've heard it once in the context of a webbrowser, the reason given was that ghc doesn't deallocate memory, that is, the gc heap only increases. I doubt it'd be hard to fix, not to mention that, iff a Haskell process is more or less the only process running on a system, deallocation becomes practically irrelevant... which'd be the case with e.g. a HAppS production server.

Any other known problems?

-- (c) this sig last receiving data processing entity. Inspect headers for copyright history. All rights reserved. Copying, hiring, renting, performance and/or quoting of this signature prohibited.

_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe