From: David Herron <David.Herron@Sun.COM>
To: David Gurvich <david.gurvich@verizon.net>
Cc: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] sun java platform independence
Date: Thu, 18 May 2006 23:45:35 -0700 [thread overview]
Message-ID: <DA9FC260-1A3B-40D4-A076-2ED69702A941@sun.com> (raw)
In-Reply-To: <200605182353.21883.david.gurvich@verizon.net>
Java works fine on my Mac ... but you're right, and I know what you
mean.
It's a matter of having appropriate VM's. I suppose a pure
interpreter VM (like what we call the "classic VM") could be portable
to pretty much any system with just a recompile. But it's from the
classic VM that Java earned the slow reputation and we really don't
want to go back there. The Hotspot VM contains compiler(s) that
dynamically compile the bytecodes to native code, so of course that's
a big dependency on specific CPU's.
And beyond the VM, there's a bunch of other native code .. such as
network I/O .. such as AWT, DnD, Sound ... Some of that is rather CPU
independant.
It's certainly very possible that, in time, this process will result
in a widely portable Java implementation. Not tomorrow. Not next
week. Not next month. Our open sourcing process is ... well...
it's going to take awhile ...
- David Herron
On May 18, 2006, at 8:53 PM, David Gurvich wrote:
> Will sun java finally become platform independent? Java is
> supposed to have
> been write once, run anywhere, but anyone using a platform other
> than sparc
> or x86 knows that it's not..
> --
> Kmail on Gentoo/PPC
> --
> gentoo-java@gentoo.org mailing list
>
--
gentoo-java@gentoo.org mailing list
prev parent reply other threads:[~2006-05-19 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 3:53 [gentoo-java] sun java platform independence David Gurvich
2006-05-19 6:45 ` David Herron [this message]
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=DA9FC260-1A3B-40D4-A076-2ED69702A941@sun.com \
--to=david.herron@sun.com \
--cc=david.gurvich@verizon.net \
--cc=gentoo-java@lists.gentoo.org \
/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