caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Dave Berry <dave@kal.com>
To: John Max Skaller <skaller@ozemail.com.au>,
	Markus Mottl <mottl@miss.wu-wien.ac.at>
Cc: OCAML <caml-list@inria.fr>
Subject: RE: JIT-compilation for OCaml?
Date: Tue, 9 Jan 2001 17:18:34 -0000	[thread overview]
Message-ID: <3145774E67D8D111BE6E00C0DF418B663AA6EC@nt.kal.com> (raw)

This view seems extreme to me.  Certainly the Java type system has faults --
lack of generics being one, lack of enumerated types another, and various
other points as well.  But surely Unicode is a useful de facto standard?
Using C syntax was a strong point -- it made the language familiar to many
people.  IMO Java syntax does avoid many of the worst aspects of C syntax
(e.g. pointers).  It's surely portable: JVMs run on many systems.  It
certainly isn't slow to compile, and a previous poster suggested that with
modern compilers run-time performance is not too bad.  You can access C or
C++ functions from Java using JNI (although you seem to be in two minds as
to whether C compatibility is desirable or irrelevant).

And this omits it's plus points, especially its utility in net programming.
Its security model is not the last word, but it's better than C, C++ or
Eiffel!  And its use of byte code ensures portability of compiled apps.

Dave.

-----Original Message-----
From: John Max Skaller [mailto:skaller@ozemail.com.au]
Sent: Tuesday, January 09, 2001 6:50
To: Markus Mottl

	It has a serious faulty static
type system, idiotic object orientation, no generics, isn't
compatible with C, uses the worst features of C/C++ syntax,
is inefficient to compile, load, and run, doesn't interface
well, uses Unicode instead of ISO-10646, has a hodge podge library,
is less portable than C, C++ or Eiffel, stuffed up finalisation ...

	Surely, Java is the worst modern language around.
It is an inexcusably travesty, when so much good theory is
around, and C compatibility is not required.



             reply	other threads:[~2001-01-10  8:27 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 17:18 Dave Berry [this message]
2001-01-11  7:00 ` John Max Skaller
2001-01-11 10:01   ` Alain Frisch
2001-01-12  7:55     ` John Max Skaller
  -- strict thread matches above, loose matches on Subject: below --
2001-01-11 12:45 Dave Berry
2001-01-12  8:23 ` John Max Skaller
2001-01-09 17:09 Dave Berry
2001-01-11  6:38 ` John Max Skaller
2001-01-03 15:24 Jerry Jackson
2001-01-04 14:12 ` Alan Schmitt
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
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

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=3145774E67D8D111BE6E00C0DF418B663AA6EC@nt.kal.com \
    --to=dave@kal.com \
    --cc=caml-list@inria.fr \
    --cc=mottl@miss.wu-wien.ac.at \
    --cc=skaller@ozemail.com.au \
    /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).