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] Industry looks for commercial OCaml support?
Date: Mon, 5 Nov 2007 05:05:42 +0000	[thread overview]
Message-ID: <200711050505.43062.jon@ffconsultancy.com> (raw)
In-Reply-To: <1194233546.27580.4.camel@rosella.wigram>

On Monday 05 November 2007 03:32, skaller wrote:
> Perl is dead... maybe *because* it lacked commercial support
> as a language.

Do you mean Perl's use in industry has declined or that it has lost market 
share even among free software languages?

We had an interesting discussion about the choice of GL library that underpins 
LablGTKGL on the LablGTK mailing list a while back. According to the Debian 
package popularity contest, Perl (and OCaml) programmers use the 
arguably-deprecated GLArea library but other (primarily Ruby) programmers use 
the newer but arguably-worse GLExt library. I concluded that Perl's 
popularity is keeping GLArea alive so there isn't too much to worry about 
LablGTKGL growing out of date.

If Perl is in decline then maybe LablGTK should move on to GLExt. Looking at 
the Ubuntu package popularity contest now, GLExt is 5x more popular than 
GLArea (33k vs 6.4k installations).

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


  parent reply	other threads:[~2007-11-05  5:15 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-04 12:01 Smoke Vector Graphics: source code licenses for sale 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             ` Jon Harrop [this message]
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
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=200711050505.43062.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