Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>,
	caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Haskell vs OCaml
Date: Thu, 14 Aug 2008 22:16:26 +0100	[thread overview]
Message-ID: <200808142216.26328.jon@ffconsultancy.com> (raw)
In-Reply-To: <1218747289-sup-9086@ausone.local>

On Thursday 14 August 2008 21:57:59 you wrote:
> Excerpts from Jon Harrop's message of Thu Aug 14 15:57:47 +0200 2008:
> > On Thursday 14 August 2008 12:50:43 blue storm wrote:
> > > and Haskell is faster than most (scripting) languages used these days
> > > anyway).
> >
> > Despite being written in Python, Mercurial is orders of magnitude faster
> > than Darcs.
>
> The difference of performances between Darcs and Mercurial is 99% due
> differences in algorithms not in the implementation language. So this
> comparison does not make sense!

Only if the choice of algorithm was independent of the language, which is 
rarely the case.

For example, Fortran programmers use arrays when they are unsuitable and their 
programs can be slower than scripting languages as a consequence. That is 
Fortran's fault.

Does the Darcs implementation overuse singly linked lists because they are 
more accessible? Are the reported stack overflows indicative of this? I don't 
know but I certainly wouldn't rule it out as a possibility.

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e


  reply	other threads:[~2008-08-14 21:15 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 12:48 circ ular
2008-08-13 13:27 ` [Caml-list] " Brian Hurt
2008-08-14  0:09 ` Jon Harrop
2008-08-14  2:46   ` David Thomas
2008-08-14  2:52     ` Erik de Castro Lopo
2008-08-14 10:37       ` Paolo Donadeo
2008-08-14 12:17     ` Jon Harrop
2008-08-14 16:44       ` Erik de Castro Lopo
2008-08-14 11:50 ` blue storm
2008-08-14 12:47   ` David Mitchell
2008-08-14 13:28   ` Peng Zang
2008-08-14 14:01     ` Peng Zang
2008-08-15  2:09       ` blue storm
2008-08-14 13:57   ` Jon Harrop
2008-08-14 14:06     ` Peng Zang
2008-08-14 14:21     ` Vincent Hanquez
2008-08-14 14:44       ` Jon Harrop
2008-08-14 20:57     ` Nicolas Pouillard
2008-08-14 21:16       ` Jon Harrop [this message]
2008-08-14 21:50         ` Nicolas Pouillard
2008-08-15  0:15           ` Jon Harrop
2008-08-15  1:14             ` Stéphane Glondu
2008-08-17  1:00             ` Luca Saiu
2008-08-19  2:40             ` Paul Snively
2008-08-20 11:33 ` Dr. Thomas Fischbacher
2008-08-21  8:47   ` DooMeeR
2008-08-21 10:59     ` David Teller
2008-08-21 13:52     ` Dr. Thomas Fischbacher
2008-08-14 13:26 Damien Guichard
     [not found] <fa.e3jKyg6bl9+vTkPgypQ4ZRzEoos@ifi.uio.no>
2013-03-18  9:08 ` adrian.alexander.may
2013-03-18  9:48   ` Malcolm Matalka
2013-03-18  9:59     ` Gabriel Scherer
2013-03-18 11:05       ` Adrian May
2013-03-18 11:26     ` Kakadu
2013-03-19  1:23       ` Francois Berenger
2013-03-26 10:36         ` Nicolas Braud-Santoni
2013-03-26  0:49   ` Kristopher Micinski
2013-03-26  2:37     ` Erik de Castro Lopo
2013-03-26  2:57       ` Kristopher Micinski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200808142216.26328.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=nicolas.pouillard@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox