From: Richard Jones <rich@annexia.org>
To: Dario Teixeira <darioteixeira@yahoo.com>
Cc: caml-list@yquem.inria.fr, Dawid Toton <d0@wp.pl>
Subject: Re: [Caml-list] What is a future of ocaml?
Date: Thu, 15 Jan 2009 17:50:45 +0000 [thread overview]
Message-ID: <20090115175045.GB3435@annexia.org> (raw)
In-Reply-To: <861603.52177.qm@web111514.mail.gq1.yahoo.com>
On Wed, Jan 14, 2009 at 09:28:59AM -0800, Dario Teixeira wrote:
> Speaking of which, there's something that's been on my mind for quite
> some time: what's the holdup preventing INRIA from having more manpower
> dedicated to Ocaml?
Honestly I don't think we need to fixate on the core compiler. If the
compiler had a new release once a year it really wouldn't matter.
Perl 5.x releases new versions less often than once a year, and that
wasn't what killed Perl take-up (it was the Osborne Effect around Perl
6 which did that, combined with O'Reilly dropping financial support).
What's needed is activity in all the other areas around the compiler -
I listed a few in my other response.
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2009-01-15 17:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 9:18 Radzevich Belevich
2009-01-14 9:35 ` [Caml-list] " David Allsopp
2009-01-14 9:51 ` Richard Jones
2009-01-14 13:34 ` Sylvain Le Gall
2009-01-14 13:44 ` [Caml-list] " Dawid Toton
2009-01-14 15:37 ` Martin Jambon
2009-01-14 15:39 ` David Allsopp
2009-01-15 12:13 ` Jacques Garrigue
2009-01-15 12:46 ` Benedikt Grundmann
2009-01-15 22:20 ` Oliver Bandel
2009-01-16 14:56 ` Kuba Ober
2009-01-15 12:51 ` David Allsopp
2009-01-15 21:08 ` Stefan Monnier
2009-01-14 16:07 ` [Caml-list] " Jérémie Dimino
2009-01-14 17:28 ` Dario Teixeira
2009-01-15 17:50 ` Richard Jones [this message]
2009-01-15 17:46 ` Richard Jones
2009-01-18 16:34 ` Xavier Leroy
2009-01-18 18:02 ` 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=20090115175045.GB3435@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@yquem.inria.fr \
--cc=d0@wp.pl \
--cc=darioteixeira@yahoo.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;
as well as URLs for NNTP newsgroup(s).