Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Google trends
Date: Thu, 1 Nov 2007 16:31:35 +0000	[thread overview]
Message-ID: <200711011631.35443.jon@ffconsultancy.com> (raw)
In-Reply-To: <20071101094629.GA28190@furbychan.cocan.org>

On Thursday 01 November 2007 09:46, Richard Jones wrote:
> This is hardly a cause to cheer.  The two languages aren't compatible
> in any way which is relevant to the real world...

The compatibility has made it easy for us to port our software in OCaml on 
Linux to F# on Windows. That is (literally) valuable to us.

> and the libraries are completely different.

Much of the F# stdlib is both compatible and improved (e.g. tail recursive) 
and extended (e.g. Array.map2). Some other aspects such as web services and 
complex numbers are better in F#. For many other things, such as FFTW, I 
write my own shim anyway and there are then no compatibility issues. Writing 
bindings is easier with F# and there are no silly Bigarrays (woohoo!) or 
anything.

> Microsoft could have contributed valuable changes back to OCaml,

As Skaller has said, we cannot contribute to the OCaml code base. Even if you 
fork the codebase you are still bound by its license and you are not allowed 
to redistribute your own modified OCaml distribution.

That is simply not viable for a corporation developing a product. We have 
considered paying to join the CAML Consortium in order to get a more liberal 
license with a view to developing a graphical top-level for OCaml like 
Mathematica's notebook front-end but licensing complications and the 
reliability of binary distributions under Linux deterred us.

> but instead decided to produce their own incompatible clone.

I'm hoping the few remaining incompatibilities between the obvious core 
language (e.g. being unable to supercede module-level definitions in F#) are 
ironed out before the first product release. The remaining differences 
(labelled and optional arguments are different, no structural subtyping 
including polymorphic variants) are sufficiently small that you can already 
port a lot of useful OCaml code to Windows quite easily and then sell it.

From a commercial perspective, it is very nice that you can sell F# DLLs 
easily. I've been wanting to sell Smoke for some time and this is the easiest 
route.

Overall, anyone interested in earning a living from programming in OCaml 
should definitely consider F#. We are already earning a significant amount of 
money from it and I only see that improving...

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


  parent reply	other threads:[~2007-11-01 16:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01  1:02 Jon Harrop
2007-11-01  2:20 ` [Caml-list] " skaller
2007-11-01  8:37 ` Oliver Bandel
2007-11-01  9:31   ` Ulf Wiger (TN/EAB)
2007-11-01 10:55     ` Oliver Bandel
2007-11-01  9:46 ` Richard Jones
2007-11-01 12:00   ` skaller
2007-11-01 12:46     ` Richard Jones
2007-11-01 15:45       ` skaller
2007-11-01 16:31   ` Jon Harrop [this message]
2007-11-01 18:12     ` Richard Jones
2007-11-01 19:47       ` Peng Zang
2007-11-02  3:11       ` Jon Harrop
2007-11-02 13:48         ` Lars Nilsson
2007-11-02 15:54           ` Oliver Bandel
2007-11-01 13:01 ` Brian Hurt
2007-11-01 16:10   ` skaller
2007-11-01 18:05     ` Richard Jones
2007-11-02  3:01       ` skaller
2007-11-02 15:50         ` Jon Harrop
2007-11-02 16:26           ` Ulf Wiger (TN/EAB)
2007-11-02 16:07         ` Language trends / Caml popularity (Re: [Caml-list] Google trends) Oliver Bandel
2007-11-01 21:00 ` [Caml-list] Google trends Dario Teixeira
2007-11-03  0:02   ` Florian Weimer
2007-11-02 22:45 ` Florian Weimer
2007-11-03  1:32   ` Jon Harrop

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=200711011631.35443.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.com \
    --cc=caml-list@yquem.inria.fr \
    /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