Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Michael Ekstrand <michael@elehack.net>
To: caml-list@inria.fr
Subject: Re: native vs bytecode
Date: Thu, 07 Aug 2008 17:12:49 -0500	[thread overview]
Message-ID: <87fxpgzd7i.fsf@jehiel.elehack.net> (raw)
In-Reply-To: <200808070913.51534.ober.14@osu.edu>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

Kuba Ober <ober.14@osu.edu> writes:
> On Thursday 07 August 2008, Kuba Ober wrote:
>> > With this strategy, OCaml programs at Red Hat are performing as well
>> > as C code, and about an order of magnitude faster & an order of
>> > magnitude lower memory usage than programs written in Python, which is
>> > the main language used around here.
>>
>> What does RedHat use OCaml for? That's just to satisfy my curiosity. A
>> quick google for ocaml at redhat did not yield much.
>
> I should say that I did look at your page, so the question should rather be:
> what does RedHat use Ocaml for, other than what RJ is using it for? :)

Educated guess based on the things listed on RJ's page and the packages
presently available in Fedora 9: tools for a future version of RHEL, I
would imagine :).

- Michael

-- 
mouse, n: A device for pointing at the xterm in which you want to type.
Confused by the strange files?  I cryptographically sign my messages.
For more information see <http://www.elehack.net/resources/gpg>.

[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]

  reply	other threads:[~2008-08-07 23:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06 19:58 Ben Aurel
2008-08-06 20:05 ` [Caml-list] " Alain Frisch
2008-08-07  1:24   ` Matt Gushee
2008-08-07 12:46     ` Richard Jones
2008-08-06 20:09 ` Peng Zang
2008-08-07  7:38   ` Ulf Wiger (TN/EAB)
2008-08-06 21:21 ` Richard Jones
2008-08-07 13:02   ` Kuba Ober
2008-08-07 13:13     ` Kuba Ober
2008-08-07 22:12       ` Michael Ekstrand [this message]
2008-08-06 21:47 ` Mauricio Fernandez
2008-08-07  0:34 ` Haoyang Wang

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=87fxpgzd7i.fsf@jehiel.elehack.net \
    --to=michael@elehack.net \
    --cc=caml-list@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