Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Richard Jones <rich@annexia.org>
Cc: Alexandre Pilkiewicz <alexandre.pilkiewicz@polytechnique.org>,
	caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Smoke Vector Graphics: source code licenses for sale
Date: Fri, 09 Nov 2007 13:16:28 +0100	[thread overview]
Message-ID: <1194610589.19355.34.camel@localhost.localdomain> (raw)
In-Reply-To: <20071108230811.GA10791@furbychan.cocan.org>

Am Donnerstag, den 08.11.2007, 23:08 +0000 schrieb Richard Jones:
> On Thu, Nov 08, 2007 at 07:28:11PM +0100, Alexandre Pilkiewicz wrote:
> > 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.
> 
> Granted, it wasn't OCaml's finest moment, but both Debian & Fedora/
> RHEL are shipping the 'old' camlp4 (now called camlp5) along with the
> new one.  So commercial enterprises depending on camlp4 from 3.09, if
> there are any, shouldn't have problems.

There is another solution: continue to use 3.09 (that's what we are
doing at Wink) and wait until the problems in the external libraries are
solved. There's no real disadvantage (for us) - 3.09 is one of the best
versions that ever existed.

If the new camlp4 was really a problem for enterprises they could also
invest time in upgrading the code. I don't see any problem here since
they got the code for free. I've already upgraded stuff to 3.10 - it's
not really that much time, very affordable for companies. Actually, this
is the type of development that tends to be boring, and companies would
be very welcome improving the motivation with money.

Before this thread continues in this style: There is nothing wrong with
O'Caml in industry - all languages have their good and bad sides, and
industry knows this. We are currently seeing a very slow adoption by
industrial pioneers. All in all this is encouraging. For speeding this
process up, the most urgent things we need are people who convince their
bosses to try this "new" technology out. Where are all the companies
that jump at every trend, and that want to present themselves as the
earliest adopters of any stuff that is ever released to mankind? - I
think it is the right moment to advertise O'Caml in this way. Make a
trend of it. A trend does not need real arguments (this can come later),
it lives for some time by itself because people don't want to miss it.

I think we should stop throwing at every O'Caml error with the
industrial argument ("this and this prevents O'Caml from being used in
industry"). We wouldn't have pioneering companies if that were true in
any way. And saying this argument too loud could really prevent possible
uses in industry - evaluations are often not based on facts, but on
reputation.

Gerd
-- 
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany 
gerd@gerd-stolpmann.de          http://www.gerd-stolpmann.de
Phone: +49-6151-153855                  Fax: +49-6151-997714
------------------------------------------------------------


  reply	other threads:[~2007-11-09 12:17 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
2007-11-08 23:08       ` Richard Jones
2007-11-09 12:16         ` Gerd Stolpmann [this message]
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=1194610589.19355.34.camel@localhost.localdomain \
    --to=info@gerd-stolpmann.de \
    --cc=alexandre.pilkiewicz@polytechnique.org \
    --cc=caml-list@yquem.inria.fr \
    --cc=rich@annexia.org \
    /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