Re: If .net and j2ee are so great...
"xx" <xxx@yyy.zzz> wrote in message news:3F44EA92.2 030602@yyy.zzz. ..[color=blue]
>
>
> Tor Iver Wilhelmsen wrote:[color=green]
> > mlw <mlw@nospam.n o> writes:
> >
> >[color=darkred]
> >>Or perhaps you don't know what you think you know. Byte codes are[/color][/color][/color]
not[color=blue][color=green][color=darkred]
> >>machine codes, they are interpreted or "JIT" compiled at runtime,[/color][/color][/color]
either[color=blue][color=green][color=darkred]
> >>way, a Java or .NET program is not in machine form.[/color]
> >
> >
> > The byte codes, whether targeting the CLR or JVM, are turned into
> > native code fractions of a second after the classes load - from that
> > point on,it's just as native as a "precompile d to native" C app.[/color]
>
> Yes, "from that point on" is a common thing to say, but not very true.
> Every time you run the program you have to re-interpret it into[/color]
machine[color=blue]
> code. It is an interpreted program, it matters not how it is[/color]
interpreted.
Actually, .NET compilations are usually cached, so they're not
compiled every time, just the once.
..NET is interpreted in the same way that C++ is interpreted into
machine code :)
[color=blue]
> If you update your JVM or CLR, it may "interpret" your byte codes
> differently. Where as my binary application will execute the same
> instructions until there is a new version. A very important[/color]
distinction.
Really? So all those DLLs you call will never change? You have
external dependencies on the system and the runtime environment.
It just happens that .NET compile code's runtime environment
is more compact and consistent across platforms.
-c
"xx" <xxx@yyy.zzz> wrote in message news:3F44EA92.2 030602@yyy.zzz. ..[color=blue]
>
>
> Tor Iver Wilhelmsen wrote:[color=green]
> > mlw <mlw@nospam.n o> writes:
> >
> >[color=darkred]
> >>Or perhaps you don't know what you think you know. Byte codes are[/color][/color][/color]
not[color=blue][color=green][color=darkred]
> >>machine codes, they are interpreted or "JIT" compiled at runtime,[/color][/color][/color]
either[color=blue][color=green][color=darkred]
> >>way, a Java or .NET program is not in machine form.[/color]
> >
> >
> > The byte codes, whether targeting the CLR or JVM, are turned into
> > native code fractions of a second after the classes load - from that
> > point on,it's just as native as a "precompile d to native" C app.[/color]
>
> Yes, "from that point on" is a common thing to say, but not very true.
> Every time you run the program you have to re-interpret it into[/color]
machine[color=blue]
> code. It is an interpreted program, it matters not how it is[/color]
interpreted.
Actually, .NET compilations are usually cached, so they're not
compiled every time, just the once.
..NET is interpreted in the same way that C++ is interpreted into
machine code :)
[color=blue]
> If you update your JVM or CLR, it may "interpret" your byte codes
> differently. Where as my binary application will execute the same
> instructions until there is a new version. A very important[/color]
distinction.
Really? So all those DLLs you call will never change? You have
external dependencies on the system and the runtime environment.
It just happens that .NET compile code's runtime environment
is more compact and consistent across platforms.
-c
Comment