Re: Java virtual machine as target language for C/C++

genew@mindlink.bc.ca (Gene Wirchenko)
13 May 1996 14:29:59 -0400

          From comp.compilers

Related articles
[9 earlier articles]
Re: Java virtual machine as target language for C/C++ sal714@rs710.gsfc.nasa.gov (1996-05-08)
Re: Java virtual machine as target language for C/C++ bnm@indica.bbt.com (1996-05-10)
Re: Java virtual machine as target language for C/C++ mbk@caffeine.engr.utk.edu (1996-05-10)
Re: Java virtual machine as target language for C/C++ Drinie@xs4all.nl (1996-05-10)
Re: Java virtual machine as target language for C/C++ dean@psy.uq.oz.au (1996-05-10)
Re: Java virtual machine as target language for C/C++ khays@sequent.com (1996-05-13)
Re: Java virtual machine as target language for C/C++ genew@mindlink.bc.ca (1996-05-13)
Re: Java virtual machine as target language for C/C++ pardo@cs.washington.edu (1996-05-14)
Re: Java virtual machine as target language for C/C++ dmoisan@shore.net (1996-05-14)
Re: Java virtual machine as target language for C/C++ rfg@monkeys.com (1996-05-19)
Re: Java virtual machine as target language for C/C++ moresys@world.std.com (1996-05-19)
Re: Java virtual machine as target language for C/C++ pardo@cs.washington.edu (1996-05-19)
Re: Java virtual machine as target language for C/C++ robison@kai.com (Arch Robison) (1996-05-21)
[8 later articles]
| List of all articles for this month |

From: genew@mindlink.bc.ca (Gene Wirchenko)
Newsgroups: comp.lang.java,comp.compilers
Followup-To: comp.lang.misc
Date: 13 May 1996 14:29:59 -0400
Organization: MIND LINK! - British Columbia, Canada
References: 96-05-036 96-05-064 96-05-069
Keywords: Java, C

mbk@caffeine.engr.utk.edu (Matt Kennel) wrote:


[snip]


>Did anybody see the Sunday New York Times? There was an article about
>economists' research on "path dependence": how some choices
>(especially in high tech) can prevent the system from reaching global
>optimum? ...


>I think you can see the implications here.


>I.e: do NOT pervert the JVM to C (and C++) semantics. That would mean
>the prolonged continuation of inferior application technology and languages.


>It might be somewhat painful at first (to have no easy C/C++ -> JVM
>converter) but I'm sure that in the long run this will be the right
>decision. No doubt a C++ converter is "possible" but if it means a 2x
>performance hit compared to java or Eiffel or Ada...


>We should adapt the JVM to the future (or at least the present capability
>of Dylan/CLOS/Smalltalk/Eiffel types of languages).


          On the other hand (I do this well being the other (left)
handed.):


          Technology develops over time. It becomes, in general, better.
So what is your point exactly wrt inferior technology at the outset?
That's when it's going to happen.


          What is the global optimum of something that keeps improving?


          If you are requiring that I have to give up my whatever-it-is for
the privilege of hobnobbing in the new society of with-it leading edge
geniuses, I just may tell you to take a hike.


          Your technology may be more advanced, but
    a) it also hasn't had the bugs all worked out.
    b) workarounds (where necessary) haven't yet been worked out.
    c) where is the software to replace my-app?
    d) where is the software period?


          I want a system that works. I value reliability and I am not the
only one. The price of the glamourous, new features may be
unglamourous crashes, lost time, etc.


          Do you remember the announcements about how OS/2 was going to
replace MS-DOS by n years ago? If one has an adequate solution, why
go elsewhere? Consider the expense! The idea that technical
superiority is the only criterion for deciding what is better is
folly. Do you upgrade your computer every month as something "better"
comes out? If yes, may I have your castoffs? I don't mind being a
month or two behind <G>.


Sincerely,


Gene Wirchenko
[Enough already on this discussion, --


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.