From: Bill Chatfield <bill_chatfield@yahoo.com>
To: Andrew Haley <aph@redhat.com>,
"classpath@gnu.org" <classpath@gnu.org>,
"java@gcc.gnu.org" <java@gcc.gnu.org>,
Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Subject: Re: Next steps for GNU Classpath
Date: Tue, 16 Sep 2014 15:47:00 -0000 [thread overview]
Message-ID: <1410882424.4959.YahooMailBasic@web124703.mail.ne1.yahoo.com> (raw)
In-Reply-To: <CABDcavZ1wZycCCh93hg1V-kNMitJTeQ=2VSOxq976-JO1URePA@mail.gmail.com>
OpenJDK is Linux-only. It does not work on Windows. This defeats the purpose of Java of being cross-platform. You might say that Windows has Oracle's Java, but it is not GPLed. It cannot be redistributed or bundled with an app. It is huge and copyrighted. When you install it, it tries to screw you over by installing the Ask Toolbar. These are problems that GCJ does not have.
GCJ & GNU Classpath are truly cross-platform, in the original spirit of Java. They have the correct copyright (GPL/LGPL) and they are redistributable/bundable with an app. As a Java developer who would like to distribute apps to users, GCJ & GNU Classpath have significant advantages over OpenJDK/Oracle.
I am not interested in switching to Java "killers" (aka Java ripoffs) like Google Go, Vala, etc, that just change the syntax enough to be annoying. I want Java.
--------------------------------------------
On Mon, 9/15/14, Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com> wrote:
Subject: Next steps for GNU Classpath
To: "Andrew Haley" <aph@redhat.com>, "classpath@gnu.org" <classpath@gnu.org>, "java@gcc.gnu.org" <java@gcc.gnu.org>
Date: Monday, September 15, 2014, 3:34 AM
Hello all,
I'm going back to this question that Andrew asked a few days
ago:
2014-09-04 22:15 GMT+02:00 Andrew Haley <aph@redhat.com>:
> Everyone: let's have a proper discussion. Is
there something we can
> do with GNU Classpath that takes it further
forward. And, if so,
> what? What would our goals be?
The following is my opinion only:
Now that we have OpenJDK, most Java users will use that on
"standard"
environments such as desktop boxes. I would say that there
is one
distinct advantage of Classpath over OpenJDK, which is its
smaller
size and footprint. This makes it an excellent choice for
embedded
systems, where OpenJDK is probably too big, and full of
features that
are not always useful in an embedded environment.
I think Classpath has an important opportunity in the
embedded world
as a "low-fat" class library for embedded JVMs.
Best,
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
next prev parent reply other threads:[~2014-09-16 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 7:34 Guillermo Rodriguez Garcia
2014-09-16 15:47 ` Bill Chatfield [this message]
2014-09-16 16:01 ` Andrew Haley
2014-09-16 18:29 ` fernando
2014-09-16 18:39 ` Andrew Haley
2014-09-16 18:54 ` fernando
2014-09-16 16:01 ` Guillermo Rodriguez Garcia
2014-09-16 19:56 ` Andïï
2014-09-16 21:04 ` Bill Chatfield
2014-09-17 7:30 ` Andrew Haley
[not found] <CABDcavYOCQcwaSzvZDr0iRLvZzdsSKBN0SH1yb0FDnrkX3C3eQ@mail.gmail.com>
2014-09-17 15:32 ` Bill Chatfield
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=1410882424.4959.YahooMailBasic@web124703.mail.ne1.yahoo.com \
--to=bill_chatfield@yahoo.com \
--cc=aph@redhat.com \
--cc=classpath@gnu.org \
--cc=guille.rodriguez@gmail.com \
--cc=java@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).