Newsgroups: comp.lang.dylan
Path: cantaloupe.srv.cs.cmu.edu!rochester!udel!news.mathworks.com!newsfeed.internetmci.com!in1.uu.net!news.abs.net!aplcenmp!hall
From: hall@aplcenmp.apl.jhu.edu (Marty Hall)
Subject: Re: Java v. Dylan (was Re: Apple Dylan discussions at WWDC)
Message-ID: <Ds4C6z.FK3@aplcenmp.apl.jhu.edu>
Organization: JHU/APL Research Center, Hopkins P/T CS Faculty
References: <ROGOFF.96May24092116@sccm.Stanford.EDU> <4oa4fp$8pg@cantaloupe.srv.cs.cmu.edu> <GTN.96May27201330@dizzy>
Date: Tue, 28 May 1996 13:59:22 GMT
Lines: 15

In article <GTN.96May27201330@dizzy> gtn@dizzy (Gavin Nicol) writes:

>There is one very good reason why Java may not be used for large,
>expensive to develop applications: it is trivial to reverse engineer a
>Java program. There are already *.class -> C translators, and given
>that the source to the VM is available, I think you'll find it to be
>very easy for people to reconstruct the control flow to a point where
>you be able to read in a *.class, and output understandable Java.

But this is only true for Java programs that will be delivered over
the Web to be run in a browser ("applets" in Java-lingo). They are
delivered in bytecodes (i.e. Java VM assembly language). But a
standalone application could be compiled to native code and delivered
the same way as other native applications.
						- Marty
