From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: e064ad9bc9,91e8dfd7d1e6fa38,start X-Google-Attributes: gide064ad9bc9,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!feeder.news-service.com!border1.nntp.ams.giganews.com!nntp.giganews.com!de-l.enfer-du-nord.net!news.visyn.net!open-news-network.org!visyn.net!not-for-mail From: "Mark T.B. Carroll" Newsgroups: comp.lang.eiffel,comp.lang.ada,comp.lang.modula3,comp.lang.pascal,comp.programming,comp.lang.haskell Subject: Re: Alternatives to C: ObjectPascal, Eiffel, Ada or Modula-3? Followup-To: comp.lang.haskell Date: Tue, 21 Jul 2009 09:25:47 -0400 Organization: Aetion Technologies LLC, Ohio, USA Message-ID: <86fxcquq04.fsf@ixod.org> References: <87zlb2c94a.fsf@galatea.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: hoshi.visyn.net OYqBjI7vdkZ53lx2L7Jty9OBfMnbp4bSyUu2hfc3/Vk= X-Complaints-To: abuse@open-news-network.org NNTP-Posting-Date: Tue, 21 Jul 2009 13:25:29 +0000 (UTC) X-User-ID: z0UFEEweHJlUBeqKLXGW0BQEmUn3f4dxJv858tRyhvo= Cancel-Lock: sha1:grMKprRu6LLlacrQzbOXqTkUIg4= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) Xref: g2news2.google.com comp.lang.eiffel:359 comp.lang.ada:7229 comp.lang.modula3:67 comp.programming:11942 comp.lang.haskell:1708 Date: 2009-07-21T09:25:47-04:00 List-Id: Jon Harrop writes: > Pascal J. Bourguignon wrote: >> Have a look at Haskell. > > He said performance was important. And it's achievable in Haskell, especially with a bunch of the work that's been done in GHC 6.6, 6.8, 6.10, and especially if you have multiple cores. (I'm not just talking about things like short cut fusion, but a bunch of library improvements like in ByteStrings.) The caveat - and you may consider it a showstopper, but I don't - is that it's easy for a newbie to write grossly inefficient Haskell. It takes some understanding of what GHC's up to and what fancy stuff is available, and some use of the profiler, to really be able to eke good performance out of the system, and you may not think it acceptable that (a) it's not easy for new users to figure out how to get good performance from it and (b) if a part of the code has to be much changed to make it fast, that part often ends up looking rather ugly. (I'd be interested to see if Haskell fans can rebut me on those points, but I bet some of the language shootout code still looks horrifying.) Admittedly, the last I looked, it may be that Data.HashTable is still slower than I'd have thought reasonable. But if I figure that if I use it anyway then someone'll fix it and I'll notice the improvement when I upgrade GHC. (-: [ followups trimmed ] Mark