From: Ernesto <ernesto.bascon@gmail.com>
To: Andrew Haley <aph@redhat.com>
Cc: java@gcc.gnu.org
Subject: Re: About gcj present and future
Date: Tue, 08 Jan 2013 17:46:00 -0000 [thread overview]
Message-ID: <CAOOf6hwVkntj0VDvhmVk=ZO0xu-Q9NgBGWfPGTjACbW+vnL6eg@mail.gmail.com> (raw)
In-Reply-To: <50EBEC84.3030509@redhat.com>
>> 3. I read somewhere that gcj is in "active maintenance mode". Does
>> that mean that we can trust it will be available in next versions of
>> gcc? Or is there some plan to discontinue it? I want to start an app
>> on it and I would want to know it will be available for several years
>> now (CNI interface is a very amazing piece of technology).
>
> Well, yes. Good question. I'd love to restart active development of
> GCJ, but OpenJDK is free software and is way ahead in terms of
> features. GCJ has some advantages, but so far these haven't been enough
> to persuade people to work on it. If we don't do something soon it
> may be too late.
Could you please elaborate more on "way ahead in terms of features"?
Which features, for example?
Must we rely on the Java Class Libraries? Providing a nice set of
classes (an alternative framework) would be a feasible way to turn gcj
into a new life? (another UI framework, implementations on top of
existing native libre/open source, etc) As I told you in my first
email, I am new on gcj so maybe the things I'm writing on are unreal,
unfeasible or completely not applicable.
> Andrew.
Thanks!
Ernesto
next prev parent reply other threads:[~2013-01-08 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 5:26 Ernesto
2013-01-08 9:53 ` Andrew Haley
2013-01-08 17:46 ` Ernesto [this message]
[not found] ` <CAOOf6hyQR4yLqR=89__cVr12U6tYzQW0POR0cwy=EUFX=fjk3g@mail.gmail.com>
2013-01-08 18:06 ` Andrew Haley
2013-01-17 19:17 bbaker
2013-01-17 19:29 ` Andrew Haley
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='CAOOf6hwVkntj0VDvhmVk=ZO0xu-Q9NgBGWfPGTjACbW+vnL6eg@mail.gmail.com' \
--to=ernesto.bascon@gmail.com \
--cc=aph@redhat.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).