Inspired by the various replies to the "haskell for non-haskell sake" I wonder why so much people uses haskell "only for prototipying" or producing code in other languages. I am just curios to hear from people who do not use haskell for project releases, or just think it's not suitable for a mature project, what exactly they find bad in current haskell implementations, or perhaps in the standard. Vincenzo
I would say that being a relatively niche technology would be a factor in not using Haskell, because finding staff to handle software maintenance is problematic. Also, I think that memory usage and performance is still an issue (real or imagined? My sense is that compiled Haskell can match widely languages like Perl or Python, but not yet Java or C/C++). #g -- At 01:46 04/09/03 +0200, Nick Name wrote:
Inspired by the various replies to the "haskell for non-haskell sake" I wonder why so much people uses haskell "only for prototipying" or producing code in other languages.
I am just curios to hear from people who do not use haskell for project releases, or just think it's not suitable for a mature project, what exactly they find bad in current haskell implementations, or perhaps in the standard.
Vincenzo
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
------------ Graham Klyne GK@NineByNine.org
On Thu, 4 Sep 2003, Nick Name wrote:
I am just curios to hear from people who do not use haskell for project releases, or just think it's not suitable for a mature project, what exactly they find bad in current haskell implementations, or perhaps in the standard.
We're not really there yet, but we're likely to have to code stuff that works fast, guaranteed, with low overhead - for instance, in real-time embedded systems for military sensor data processing. I don't know where Haskell currently is, but I'm far from certain that it's up to that task. -- Mark
--- Mark Carroll
On Thu, 4 Sep 2003, Nick Name wrote:
I am just curios to hear from people who do not use haskell for project releases, or just think it's not suitable for a mature project, what exactly they find bad in current haskell implementations, or perhaps in the standard.
We're not really there yet, but we're likely to have to code stuff that works fast, guaranteed, with low overhead - for instance, in real-time embedded systems for military sensor data processing. I don't know where Haskell currently is, but I'm far from certain that it's up to that task.
What about Embedded Gofer? ;-) "Lambdas in the Liftshaft" by Malcolm Wallace. Then there's the DARPA-funded Project Timber at OGI: http://www.cse.ogi.edu/PacSoft/projects/Timber/Default.htm Chris Milton
participants (4)
-
Christopher Milton -
Graham Klyne -
Mark Carroll -
Nick Name