From: Brian Hurt <bhurt@spnz.org>
To: Ocaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] Great Programming Language Shootout Revived
Date: Thu, 17 Jun 2004 13:05:12 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0406171237270.4305-100000@localhost.localdomain> (raw)
Thought I'd point this article out for the people who've stopped reading
slashdot:
http://developers.slashdot.org/article.pl?sid=04/06/16/1622211&mode=nested&tid=126&tid=156&tid=185&tid=90
The original GPLS was the best advertising Ocaml ever had. It's why I
learned Ocaml- I discovered the original GPLS and started noticing Ocaml
ranking among the top scorers for fastest execution, least memory used,
and fewest lines of code, and said to myself "I've got to check that
language out- obviously there's something going on there."
What's starting to happen, now that the project has started up again, is
advocates/supporters of other languages have started to submit improved
versions of the code for their languages. For example, I notice that
Ocaml has dropped from it's #1 place in least lines of code to #2, with
Ruby taking the lead.
I don't think we need to make a big thing out of this (hey, #2 across the
board is pretty damned good- we're beating both Java and C++ across the
board, in fact the only other language that comes close to Ocaml's
performance is, unsurprisingly, version of SML- MLton and SML/NJ). But if
you have some spare time, and want to help out Ocaml's marketing, wander
over.
--
"Usenet is like a herd of performing elephants with diarrhea -- massive,
difficult to redirect, awe-inspiring, entertaining, and a source of
mind-boggling amounts of excrement when you least expect it."
- Gene Spafford
Brian
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2004-06-17 17:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 18:05 Brian Hurt [this message]
2004-06-18 1:18 ` Yaron Minsky
2004-06-18 9:37 ` Sebastien Ferre
2004-06-18 15:45 ` Brian Hurt
2004-06-18 21:39 ` Eray Ozkural
2004-06-18 6:09 ` Brandon J. Van Every
2004-06-18 7:56 ` Ville-Pertti Keinonen
2004-06-18 8:59 ` skaller
2004-06-18 9:57 ` Ville-Pertti Keinonen
2004-06-18 10:48 ` Implementing DSLs in OCaml/CamlP4 (was: Re: [Caml-list] Great Programming Language Shootout Revived) Richard Jones
2004-06-18 12:32 ` Walid Taha
2004-06-18 15:38 ` [Caml-list] Great Programming Language Shootout Revived Brian Hurt
2004-06-18 17:07 ` David Brown
2004-06-19 0:26 ` Nicolas FRANCOIS
2004-06-19 9:04 ` [Caml-list] Benchmark suggestion (Was: Programming Language Shootout) Wolfgang Müller
2004-06-19 10:54 ` Ville-Pertti Keinonen
2004-06-19 19:38 ` [Caml-list] Benchmark suggestion Brandon J. Van Every
2004-06-19 20:08 ` Brian Hurt
2004-06-19 20:16 ` Wolfgang Müller
2004-06-20 11:24 ` [Caml-list] Evangelism Brandon J. Van Every
2004-06-19 11:18 ` [Caml-list] Great Programming Language Shootout Revived Ville-Pertti Keinonen
2004-06-19 11:56 ` Nicolas Janin
2004-06-19 12:51 ` Marcin 'Qrczak' Kowalczyk
2004-06-19 19:46 ` Brandon J. Van Every
2004-06-19 20:19 ` Brian Hurt
2004-06-19 12:09 ` Nicolas Janin
2004-06-19 12:48 ` John Hughes
2004-06-19 18:57 ` Brian Hurt
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=Pine.LNX.4.44.0406171237270.4305-100000@localhost.localdomain \
--to=bhurt@spnz.org \
--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