From: Markus Mottl <mottl@miss.wu-wien.ac.at>
To: "Joseph R. Kiniry" <kiniry@acm.org>
Cc: OCAML <caml-list@inria.fr>, Mattias Waldau <mattias.waldau@abc.se>
Subject: Re: JIT-compilation for OCaml?
Date: Wed, 3 Jan 2001 19:19:03 +0100 [thread overview]
Message-ID: <20010103191903.B29666@miss.wu-wien.ac.at> (raw)
In-Reply-To: <49780000.978544197@kind.kindsoftware.com>; from kiniry@acm.org on Wed, Jan 03, 2001 at 09:49:57 -0800
On Wed, 03 Jan 2001, Joseph R. Kiniry wrote:
> > No, I don't use it at all, but I believe you that it must be very
> > painful ;)
>
> Not to go offtopic, but I'd rather see list members educated rather than
> FUD'ded. If ML is a Prius we still have to respect the Taurus that is Java.
There was a smiley after my criticism... - anyway, though I'd never want
to switch to Java when I can use OCaml, it isn't this bad compared to
other mainstream languages. At least some major insanities have been
removed.
> In fact, one of my companies chose Java over five competitor languages
> (Objective-C, C++, Eiffel, CLOS, and oTcl) in a head-to-head test. Note
> that this company is a group of uber-geeks with a language geek at the helm
> (me), so we were not working in a vacuum.
Why didn't you compare to OCaml or other FPLs (e.g. Haskell, Clean, etc.)?
Business reasons?
> Certainly the breadth and growth of Java's libraries is a marvel, but I
> *certainly* wouldn't say that they are a uniform example of good design.
> It amazes me that a package can go through so much semi-public design
> review and still have serious design flaws. Until one uses a library on
> large projects with many people for a some reasonable period of time,
> claims of excellence, esp from the library vendor, are premature.
It would be interesting to know what (except for GUI-stuff) people are
missing in OCaml or other FPLs. I just haven't used Java often enough
to know details about its libraries.
- Markus Mottl
--
Markus Mottl, mottl@miss.wu-wien.ac.at, http://miss.wu-wien.ac.at/~mottl
next prev parent reply other threads:[~2001-01-04 13:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 16:07 Markus Mottl
2001-01-02 18:16 ` Mattias Waldau
2001-01-02 19:30 ` Markus Mottl
2001-01-03 12:15 ` Alain Frisch
2001-01-04 8:37 ` Fabrice Le Fessant
2001-01-04 9:04 ` Alain Frisch
2001-01-03 13:23 ` Mattias Waldau
2001-01-03 14:25 ` Markus Mottl
2001-01-03 14:40 ` STARYNKEVITCH Basile
2001-01-03 15:51 ` John Max Skaller
2001-01-03 17:50 ` Markus Mottl
2001-01-05 0:30 ` Michael Hicks
2001-01-08 9:59 ` Xavier Leroy
2001-01-09 6:40 ` John Max Skaller
2001-01-03 17:49 ` Joseph R. Kiniry
2001-01-03 18:19 ` Markus Mottl [this message]
2001-01-03 18:38 ` Joseph R. Kiniry
2001-01-03 18:58 ` Markus Mottl
2001-01-03 19:06 ` Joseph R. Kiniry
2001-01-04 22:32 ` Jonathan Coupe
2001-01-07 0:16 ` Chris Hecker
2001-01-05 12:52 ` Sven LUTHER
2001-01-05 20:08 ` Joseph R. Kiniry
2001-01-09 7:14 ` John Max Skaller
2001-01-09 6:50 ` John Max Skaller
2001-01-05 12:39 ` Sven LUTHER
2001-01-05 5:48 ` Vitaly Lugovsky
2001-01-03 15:24 Jerry Jackson
2001-01-04 14:12 ` Alan Schmitt
2001-01-09 17:09 Dave Berry
2001-01-11 6:38 ` John Max Skaller
2001-01-09 17:18 Dave Berry
2001-01-11 7:00 ` John Max Skaller
2001-01-11 10:01 ` Alain Frisch
2001-01-12 7:55 ` John Max Skaller
2001-01-11 12:45 Dave Berry
2001-01-12 8:23 ` John Max Skaller
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=20010103191903.B29666@miss.wu-wien.ac.at \
--to=mottl@miss.wu-wien.ac.at \
--cc=caml-list@inria.fr \
--cc=kiniry@acm.org \
--cc=mattias.waldau@abc.se \
/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