From: Brian Hurt <bhurt@janestcapital.com>
To: Alexandre Pilkiewicz <alexandre.pilkiewicz@polytechnique.org>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Smoke Vector Graphics: source code licenses for sale
Date: Thu, 08 Nov 2007 14:14:43 -0500 [thread overview]
Message-ID: <47336023.6010808@janestcapital.com> (raw)
In-Reply-To: <200711081928.11501.alexandre.pilkiewicz@polytechnique.org>
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
Alexandre Pilkiewicz wrote:
>Le Sunday 04 November 2007 17:12:01 skaller, vous avez écrit :
>
>
>>Lack of commercial support -- the kind Jon is offering --
>>is one of the impediments to industry taking Ocaml seriously.
>>
>>
>
>
>Don't you think the worst problem for the industry is the lack of
>retro-compatibility ?
>
>Between 3.09 and 3.10 (a *minor* version number change), a lot of program
>using camlp4 stopped compiling. If a company has a 100 000 lines code (or
>more) to revise just for that, it could be kind of a problem.
>
>And so many things are just unspecified. I know it's a bad idea, whatever
>language you use, to rely on the order of evaluation of the argument of a
>function, but to say "this order may change one day" is to tell
>industrialists : "if you have some "not so good" programmers, even if you
>make all the test you want on your program to check it works, one day it may
>just stop working because we changed the order or evaluation, or worst, a lot
>of silent bugs can appear".
>
>
Which explains why industry is so wary of languages like Java and C++,
and refuses to adopt them.
Oh, wait.
Seriously, you can protect against a "not so good" programmer. Java
tried, they really tried. But you can't have decent performance and
absolute reproducability- as Java discovered with floating point numbers
and memory behavior in a multi-threaded program, among other problems.
Witness all the rants about Java's "Write once, debug everywhere" problems.
One thing I really like about Ocaml is that if order of evaluation is
important, it gives me a way to enforce a specific ordering. And it's
not even an obscure part of the language (let/in definitions).
Brian
[-- Attachment #2: Type: text/html, Size: 2220 bytes --]
next prev parent reply other threads:[~2007-11-08 19:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 12:01 Jon Harrop
2007-11-04 15:06 ` [Caml-list] " Oliver Bandel
2007-11-04 16:12 ` skaller
2007-11-04 16:48 ` Oliver Bandel
2007-11-04 17:45 ` skaller
2007-11-04 21:29 ` Oliver Bandel
2007-11-04 17:47 ` David Allsopp
2007-11-04 21:25 ` Oliver Bandel
2007-11-04 16:58 ` Industry looks for commercial OCaml support? Oliver Bandel
2007-11-04 17:52 ` [Caml-list] " skaller
2007-11-04 21:39 ` Oliver Bandel
2007-11-05 3:32 ` skaller
2007-11-05 3:58 ` OT: Commercial Support and Programming Languages Robert Fischer
2007-11-05 5:04 ` [Caml-list] " Jon Harrop
2007-11-07 15:55 ` Alan Falloon
2007-11-07 16:07 ` [Caml-list] " Jon Harrop
2007-11-07 16:35 ` Edgar Friendly
2007-11-07 16:41 ` Jon Harrop
2007-11-07 17:16 ` Edgar Friendly
2007-11-07 18:46 ` Christophe TROESTLER
2007-11-07 19:28 ` Richard Jones
2007-11-05 7:22 ` [Caml-list] " skaller
2007-11-05 5:05 ` [Caml-list] Industry looks for commercial OCaml support? Jon Harrop
2007-11-04 18:29 ` [Caml-list] Smoke Vector Graphics: source code licenses for sale Vincent Hanquez
2007-11-08 18:28 ` Alexandre Pilkiewicz
2007-11-08 19:09 ` Luc Maranget
2007-11-08 20:24 ` Alexandre Pilkiewicz
2007-11-08 20:53 ` Edgar Friendly
2007-11-08 23:04 ` Oliver Bandel
2007-11-08 19:14 ` Brian Hurt [this message]
2007-11-08 23:08 ` Richard Jones
2007-11-09 12:16 ` Gerd Stolpmann
2007-11-09 12:31 ` Richard Jones
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=47336023.6010808@janestcapital.com \
--to=bhurt@janestcapital.com \
--cc=alexandre.pilkiewicz@polytechnique.org \
--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