From: Guillermo Rodriguez Garcia <email@example.com>
To: Andrew Haley <firstname.lastname@example.org>,
Subject: Next steps for GNU Classpath
Date: Mon, 15 Sep 2014 07:34:00 -0000 [thread overview]
Message-ID: <CABDcavZ1wZycCCh93hg1V-kNMitJTeQ=2VSOxq976-JO1URePA@mail.gmail.com> (raw)
I'm going back to this question that Andrew asked a few days ago:
2014-09-04 22:15 GMT+02:00 Andrew Haley <email@example.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.
Guillermo Rodriguez Garcia
next reply other threads:[~2014-09-15 7:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 7:34 Guillermo Rodriguez Garcia [this message]
2014-09-16 15:47 ` Bill Chatfield
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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).