[1500] in java-interest
Systems Programming Oriented Java
daemon@ATHENA.MIT.EDU (John D. Mitchell)
Wed Sep 6 06:54:47 1995
Date: Wed, 6 Sep 1995 01:09:57 -0700
From: "John D. Mitchell" <johnm@emf2-003.emf.net>
To: "John D. Ramsdell" <ramsdell@linus.mitre.org>
Cc: java-interest@java.sun.com
In-Reply-To: <199509051030.GAA20199@bauhaus.mitre.org>
John D. Ramsdell writes:
[...]
> I propose the creation of a new dialect of Java, called J, intended
> for systems programming. J should be carefully designed so that it
> syntactically looks like Java and has similar semantics. With a
> little care, programmers should be able to write J programs that can
> be run and debugged as if they are ordinary Java programs.
'J' is already taken.
The question I have is... why?
C already exists and is supported *everywhere*. C++ exists in some bizarre
form or another all over the place? So why are you wanting to throw away a
bunch of the real benefits of Java just to bring back the 'dark ages' of
C/C++. Worse yet, making it so close to Java is, IMHO, a Bad Thing(tm) as
it will induce more confusion than it will help.
Why not just write ISO/ANSI/POSIX/etc. conformant C code which are
(trivially?) wrapped in Java classes. Then you have everything you need to
write OS level utilities (though device drivers would be a trick) in Java
itself. If someone did a good job on such a project it would probably get
scooped up into a standalone Java system pretty quick, etc.... :-)
Take care,
John "Why do things halfway?" Mitchell
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
