Slashdot Log In
GNU Christmas Gift: Free Eclipse
Posted by
CowboyNeal
on Thu Dec 26, 2002 06:17 PM
from the compile-once-run-sort-of dept.
from the compile-once-run-sort-of dept.
Mark Wielaard writes "Your friendly neighbourhood GNU did
it again. A year ago IBM made much noise
about placing $40 million of its software tools under a free software
license. Technically these tools, called Eclipse, are great for developing
(java) software. There was only one catch, it was build on top of the
proprietary java platform. This made it useless for the Free
Software community. Luckily the GNU project has two projects that come
to the rescue. GNU
Classpath, core libraries for java, and gcj, the GNU Compiler for Java.
We are now able to run Eclipse on a completely free platform! It is
not yet complete, but you can already edit, compile and browse CVS
with it. And since Eclipse uses GTK+ it also looks very nice. I setup
a page with
instructions on how to get this working so you can help us make
it work even better or just so you can view a couple of nice screenshots."
This discussion has been archived.
No new comments can be posted.
GNU Christmas Gift: Free Eclipse
|
Log In/Create an Account
| Top
| 320 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
I'm glad... (Score:2)
sun and java (Score:2)
Free Software Community (Score:3, Insightful)
Hmm.
combo (Score:2)
Re:Keep the zealotry to yourself (Score:5, Informative)
Incorrect in every regard.
Microsoft has already used patents to attack open source projects, and has also used patent licenses to attack the GPL. Microsoft's highest executives have also stated publically that they intend to use patents against certain open source projects.
Examples
- no translation of ASF, WMA and WMV files to any other format.
- patent licenses granted only to non-GPL software
CIFS implementations
- royalty fees on file sharing extensions to SMB in Win2K and WinXP
- Nasty letters to certain Linux kernel developers working on NTFS support.
The Halloween documents also mention the possibility that Microsoft may use Patents to attack OS endeavors.
We also have comments from Mr. Ballmer regarding
Responding to questions about the opening-up of the
And we also have this:
Asked by CollabNet CTO Brian Behlendorf whether Microsoft will enforce its patents against open source projects, Mundie replied, "Yes, absolutely." An audience member pointed out that many open source projects aren't funded and so can't afford legal representation to rival Microsoft's. "Oh well," said Mundie. "Get your money, and let's go to court."
Any statement that Microsoft has not and is not likely to enforce patents in these areas is just not backed up by the history, or by public statements by MS senior executives.
Whoopi (Score:3, Insightful)
Yeah, let's maybe stop making that ridiculous association between software, politics, the fate of humankind and the pursuit of life, liberty and freedom. It's just software. They're just computers.
Free: because everything else costs money and that sucks!
Thanks Santa (Score:1)
Running Eclipse with gcj/gij (Score:5, Insightful)
It is possible to run Eclipse with gcj since it comes with gij (GNU Interpreter for Java). It does take a little bit of work to get it running since you have to apply some patches to the latest gcj CVS verson. Hopefully the needed patches will make it into CVS soon. It is currently a bit slow (you will need a fast processor, 1Ghz+ recommended) and needs much memory (256MB recommended). And not everything will work yet (it sometimes hangs). But is already useful for gcj bug hunting and making pretty screenshots.
If you just want to know why gcj is so cool, please read: Compiling Java with GCJ by Per Bothner (Learn how gcj can not only be used to compile java programs, but also Scheme and XQuery to native code.) If you are interested in other Free Software running on top of gcj, please checkout RHUG setup by Anthony Green. (It contains precompiled binaries of things like Jakarta Tomcat, Ant, Rhino, Postgresql JDBC drivers, Jython, Xalan, Xerces, and much more.)
It took much effort to get this far with our free java platform. And I want to thank all GNU Classpath and gcj hackers for their years of hacking to make this possible. In particular I want to thank Tom Tromey the main libgcj maintainer for his guidance. And for being the first person to get to the Eclipse Welcome Screen, after all his hacking the rest was easy.
I should also mention Vincent Partington and Erwin Bolwidt for explaining why I should care about Eclipse and for their bughunting help last weekend. Please checkout their free software projects, Jaxup.
How you can help: If you write free java software make sure it works well on the GNU platform and if you like hacking on low level stuff help us make Classpath and gcj even better. And please consider to "Join us now and share the software".
The following pages explain how to patch gcj and setup Eclipse. And show some pretty screenshots of Eclipse in action.
What do you need
If you want to run it yourself you should be familiar with compiling gcj from source (either current mainline or the gcc-3_3-branch) and you will need to apply the following patches.
These patches (except the verify.cc change) should be applied to CVS soon so you might not need them.
Update: The following new patches are highly recommended.
That last patch will optimize classloading for Eclipse that doesn't need any natively compiled classes but should not be used for normal gcj usage. The other patches will hopefully make it into CVS soon.
Update: eclipse.patch [klomp.org] contains all the above patches plus a few tweaks for getting Eclipse to work better on the IKVM.NET VM [weblogs.com]. With all these patches applied I was able to open, edit and compile the Jaxup Java XML Update engine project from my friend Erwin Bolwidt inside Eclipse. The new screenshot looks nice.
When you have build and installed the new GCC you will need to make the following changes to the install.
Go inside the bin directory of the new GCC install and make a java symlink to the gij program. (Eclipse expects a binary called java, you can give the -vm gij option, but then it won't autodetect gcj as Standard VM.)
Copy the share/java/libgcj.jar file to lib/rt.jar. Then create a directory jre/lib/ and make another copy of the rt.jar here. (Note that these cannot be symlinks.)
Make a directory src and copy the gnu, java, javax and org directories from the libjava source directory in it. Then create a src.zip file which contains this src directory. Put this src.zip file in the parent directory of the dir you installed the new GCC in. So if you installed in
This is all needed because eclipse expects a tradition java environment. It should be easy to hack org/eclipse/jdt/internal/launching/StandardVMType
Update: The following is no longer needed with the latest patches.
Disable the garbage collector by export GC_DONT_GC=1. If you don't do this eclipse will not startup properly and you will find a stacktrace in the workspace/.metadata/.log file mentioning a InvocationTargetException caused by a NullPointerException.
Finally get the latest stable Eclipse build (you want the eclipse-SDK-M4-linux-gtk.zip.) It will create a directory eclipse and comes with all the sources (and a precompiled binary and the classes in jar files).
Running it
Make sure that the freshly compiled gij (and the java symlink) is in your path and that LD_LIBRARY_PATH points to the newly installed lib directory. Go inside the eclipse directory and you should be able to just type
This will take several minutes. If anything goes wrong start it with
After several minutes you will see the following welcome screen.
One of the first things you probably want to do is set the correct key bindings
Not everything will work as expected and sometimes you are greeted with the following dialog.Which is often because the garbage collector is disabled. My machine quickly gives up after eclipse has eaten more then 600MB.
Update: There used to be a screenshot here of the terminal window showing lots of Out Of Memory messages. But with all the new patches this does not happen anymore.
I havn't been following Eclipse in a while (Score:1)
so what? (Score:1, Flamebait)
So what? Does Eclipse perform any better or is Eclipse materially different using these "free" libs? Is this going to single a massive take-up of Eclipse? Or is this yet another silly political/ideological stance taken to extremes?
Eclipse is an outstanding tool - the Visual Studio of the non-microsoft world. It's used everywhere from single home based coders through to commercial "Enterprise" projects. I think the real point to write home about is that IBM has opened the next version of what is essentially the VisualAge codebase, in such a way that it can be extended and used independently of IBM.
Time spent writing Eclipse plugins rather than making it ideologically 'clean' would be of far more benefit, IMO.
Not Ready? Its all about the plugins. (Score:4, Informative)
Xored Web Studio (Score:1)
Why should I use Eclipse instead of Emacs + JDE? (Score:1)
Re:Why should I use Eclipse instead of Emacs + JDE (Score:5, Funny)
Re:Why should I use Eclipse instead of Emacs + JDE (Score:5, Informative)
Eclipse is an IDE without all the crap you usually associate with an IDE. JDE isn't bad, but it's nothing like Eclipse. Eclipse's debugging support in particular is way better than JDEs (which took me some hours to configure properly). Not to mention that Eclipse let's you do really neat things, like stop the debugger right before an exception was thrown, fix the bug, and continue with the debugging as if nothing had happened!
Java on the client-side needs this to compete... (Score:5, Interesting)
Up to this point, Sun has ignored the client-side, and rightly so. Because Microsoft and MFC rules on the client side (on Win32). Sun exploited the server-side breach that Microsoft had ignored.
But now, Java needs to become a viable alternative to C++ based programming on the client-side. And the only way this is going to happen is for Java to have some kind of a native GUI presence on each platform it runs on. This is where IBM and the SWT libraries come in.
Currently, the SWT libraries are still immature. The Eclipse platform itself is still immature. But they will get better and better. I predict that the SWT libraries will not only get quite expansive... but include things other than GUI widgets/toolkits.
If IBM plays their cards right (and so far they have)... I can see them actually introducing more Java extension libraries for other things that Sun did a terrible job on. Collections. Better native threading model. Better I/O model. The list goes on and on.
Personally, I would have no problem with writing a Java application that only imported IBM extension libraries. As long as they were well-written, and performed well.
Sun really needs to get on the ball here. The time has come to open-source Java. Let the developers do with the language what needs to be done to bring it to the next level.
Otherwise... companies like IBM are going to do it anyways. Just using extension libraries. If Microsoft was smart, they'd have done five years ago what IBM is doing now. Microsoft would own Java on the client-side if they would have played it right.
I disagree in many respects (Score:4, Insightful)
"Microsoft and MFC rules on the client side (on Win32)".
MFC is dead, long live
"But now, Java needs to become a viable alternative to C++ based programming on the client-side."
Absolutely not. Java's only main competitor for Win32 client-side supremacy is VB.NET and C#.NET. C++/MFC is a dead-end.
On UNIX, I would suggest it's a toss-up between C++/Qt and C/GTK, and IMHO I think Java's more productive than either (though pre-1.4 X-windows Swing performance was unacceptable).
Sadly, this doesn't seem to be a battle that Java will win on Win32, even with SWT, for a couple of reasons. Microsoft has the industry's talent in developing high-performance Win32 GUI framewords, which will come out for
They also have the tools support with Visual Studio. The Java world currently has only *ONE* usable GUI building tool -- JBuilder. And that's not saying much. Eclipse won't have one for some time. The second major problem with Swing (besides performance) was this lack of tools support. I don't forsee a groundswell of tools support for SWT from multiple vendors.
Thirdly, there isn't a whole lot of impetus behind client-side "thick" GUIs in the industry. I don't foresee IBM throwing lots of money at making SWT general-use... the open source community will probably assist in this area, but I'm somewhat skeptical about how much adoption this will generate.
On the bright side, I'm not sure it really "matters". Windows peeps will write stuff with VB like they've always done, the C++'ers will switch to C# (they've really not much choice -- I worked at an MS shop as the Java junkie for 2 years, most C++/Windows programmers there took what MS has given them... there's a lot of shock and dismay when Borland/OWL is on one's resume). The 2nd most widely used GUI framework family will be (gasp) Carbon/Cocoa on Mac OS X. ANd rounding out the list, *nix peeps will continue head-butting between Qt and GTK+ (both of which are still gawdawfully ugly IMHO, quite apparent actually if you run a GTK+ app side-by-side with a Mac OS X application. But I digress).
"I can see them actually introducing more Java extension libraries for other things that Sun did a terrible job on. Collections. Better native threading model. Better I/O model. The list goes on and on."
Whoa, whoa! I disagree with each one of these. We are talking about J2SE 1.4, are we not? I'm quite happy with the collections framework (and I compare this to both stdc++ and the Smalltalk collections library), the java.nio.* package is very sophisticated, and IMHO the threading model is a matter of taste, not stemming from any particular technical disadvantage.
.NET in a nutshell (Score:4, Informative)
Here's the things that it isn't (in reality):
- A new server platform (MIcrosoft marketed it as such, even though there really isn't anything new in their Windows 2000 lines of servers yet).
- A some new magic technology (i.e. the marketing idea that MS Passport became Passport.NET and thus was embued with a +6 long-sword)
Here's what it is:
- The common type system, language spec, and language interface. (CTS, CLS, and CLI). It's a way of getting several languages to interoperate through a virtual machine.
- The Common Language Runtime (CLR) for Win32. This is the Virtual Machine. It's as fast as Java 1.4 in some ways, slower in some ways, and over 2x faster at certain operations like object creation. Ya gatta hand it to Microsoft's x86 team, they know their stuff.
- The following languages are released by Microsoft for
- The Base Class Libraries (BCL), ASP.NET, COM+ (aka Managed Components), and ADO.NET are included.
- The ECMA standards body has been submitted the CLI, CTS, CLS, BCL, and C#. Mainly for show, but maybe something good may come from Miguel et al.
What's
- It's a much better way for binary module interoperability than COM was. Viewed this way,
The language-interop issue at first glance seems like a red herring feature, but in fact it's rather important from a programmer's sociological perspective. VB and C++ programmers are naturally opposed to each other in philosophy - their means and ends do not peacefully coexist.
Things you can do with
- The Windows Registry is NO LONGER NEEDED. Nothing in
- Easy and Flexible Side by side versioning. An app that links against a version stays with that version unless updated or a sysadmin coerces it to use a newer DLL version.
- No filename conflicts (i.e. no 2 vendors with MYSILLYLIBRARY.DLL overwriting each other -- each DLL has a public key stamp)
Other things... Making web services in
So -- you see,
The jury's still out as to whether
I say it's more about "syntax skin" than "flexibility". Certainly you can write Lisp onto
The license incompatibilities are still there (Score:1)
I don't think this will be a problem with the Classpath library, since iits license provides the "library exception", but in general it will make linking with other GPL licensed software a hassle.
Don't get me wrong, I like Eclipse and use it a lot. It's faster and better looking than Netbeans (plus I have no use for the GUI builder part of Netbeans), and SWT is a great idea. I'm just pointing out that there are still license incompatibilities lying around between major free software projects (remember the Python licensing controversy?), and wish that copyright holders will do something to resolve them.
Just use Anjuta (Score:4, Interesting)
Waste of Effort (Score:5, Interesting)
I think that the Java libraries will be very difficult to control fully by Sun, because they do not have IBM and Oracle to push around. IBM will absolutely not be backed into a corner by one of their main competitors in hardware, Sun. Because of that, I'm not worried about the Java APIs turning into a controlled arena, as Microsoft has done with Windows.
Basically, I think the effort of the Open Source community, of those that like Java, would be much pretty spent on making GCJ integrate seemlessly with a compliant Java VM using JNI. GCJ could used to make a just-of-time optimizer. With C# and dotNet, I think there's an ahead-of-time compiler instead of a just-in-time compiler that can optimize the byte code for the target machine. Using GCJ/GCC, one could get that sort of performance boost, almost for free, if it were plugged into a compliant Java VM, meaning that it could integrate with DLL/DSOs using the Java Native Interface.
Anyway, I, for one, would probably not waste my time using a slightly out-of-date API, on a slightly behind-the-curve VM or compiler. (BTW, I'm a heavy user of emacs, perl, mozilla, etc.) The java API, language and VM still has a LOT of room for improvement. I hope developers would rather innovate and improve the java standard than to fork off a clone.
Re:Waste of Effort (Score:4, Interesting)
I'd like to see a Free clone of Java, and then a community develop around the clone to CHANGE it into a better language. For instance, I'd like to see templates ("generics") added to java. I'd like to see type-safe enums. I'd like to see some "syntactic sugar" to make programs easier to write and read (hello, iterators). I'd like to see a GNU/Java implementation that has all this stuff and more, but is still backwards compatible with Sun/Java.
I'd like to see native-code only Java. I'd like to see GTK+ bindings for Java. I'd like to see all the old library cruft cleared out of Java. Heck, I'd like to see Java pre-installed on Red Hat, without coming on a separate CD with a separate license and a crappy RPM that was made by Sun. I wish it was available on FreeBSD sooner. I wish a lot of stuff that's only possible or easy with third-party implementations.
Old news (Score:2, Informative)
Nevertheless, this is the best tool I've used, and really, thanks IBM for doing such a great and generous job. My point is - this is not really news, and have nothing to do with Christmass.
Cheers.
GCC vs GCJ? (Score:2)
Useless to RMS, maybe (Score:5, Insightful)
If you define the "Free Software community" as the zealotous 5% of free software users who refuse to use software that hasn't been blessed by RMS, you're right.
For the rest of us, Eclipse has been useful (and free and open source) for over a year.
Re:Useless to RMS, maybe (Score:4, Insightful)
This statement is heresy ONLY if you believe Free Software and RMS are synonymous. I believe they are not. Free Software existed well before RMS, and will exist well after he is gone. He only "created" Free Software if you accept his conceit that Free Software is only software that follows his definitions of Free [gnu.org]. I do not. He has contributed a lot to this world, but didn't invent the world. Many people don't realize that The Cathedral and the Bazaar [tuxedo.org] wasn't necessarily contrasting the development styles of commercial software vs. free software, but different styles of development within Free Software itself, and the RMS driven gcc was the example of the "closed" Cathedral. Because of the lack of innovation in gcc, especially around the time ANSI C++ came out and it needed large changes, folks forked gcc into egcs, a more "bazaar" style development model, that eventually became the offical gcc. Or are you saying Eric Raymond has nothing to say on the topic of Free Software because he differs with RMS?
Or if this was a troll, nevermind.
Give me a break (Score:4, Interesting)
There is plenty of java code that has been released under the GPL and BSD licenses. The only way that java would be useless to someone is if they turned their nose up at it. Turning one's nose up at something for non-technical reasons is usually a bad idea.
Lee
The point (Score:5, Insightful)
The point that so many have missed is that this shows how close the GNU implementations are to be being a complete JDK replacement. Eclipse is a very complex beast that uses nearly all of the Java APIs. This achievement shows the quality of the years of work that has gone into these free projects. All of this work is now finally ready to pay off.
Congratulations to the whole ClassPath and GCJ teams!
-Avery Regier
Questions (Score:1)
Damn (Score:2)
How Eclipse/SWT saved the GCJ project (Score:4, Insightful)
Compiling your application to a single binary (or
Java doesn't suck. Java's GUIs need not be slow. It was Swing that sucked. Finally people realize where to lay blame.
Sun - get rid of Swing once and for all! Swing is a poorly designed GUI tookit and a complete embarassment to Java.
Useless how? (Score:1)
And all free code developed in Eclipse can be used in a future free java version. If somebody developed a propriatory java processor in silicon, would Eclipse still be useless? Saying Eclipse is useless for free development is like saying Linux is useless on the Intel platform because the Intel microcode isn't free.
Intellij IDEA, is the king of the hill. (Score:1)
Ah, Java (Score:2)
I have to say it (Score:1)
I have a dream (Score:2)
I can already see problems arising with Mono in that I simply don't trust MS not to try and kick it in the balls with a patent suit after it has started to become widely used.
Java is easy to use and secure, and at the moment, on cellphones which have Java bytecode instruction sets in their CPU's, is anexcellent opportunity for expansion. Cellphones are a booming market and present a real chance for Java on the client side with J2ME. Being able to compile to native code would make it even better suited for that purpose. MS knows how important the Cellphone market is which is why they are up to their tricks and abuse there again (Sendo) and which is why almost all Cellphone makers are giving MS a wide berth and are using Symbian, which brings the story back to Java...
Starting with Eclipse; Help a newbie! (Score:2)
Maybe you have books to recommend. Please provide any helpfull info you got (libraries to suggest, tricks, etc...) that would help a newbie to jump start quickly on this platform.
Aww man! (Score:2)
Proprietary platform (Score:2)
Free? You don't know the meaning of free. (Score:1)
So, if you mean free as in NO ONE USES IT, sure. If you mean free as in I CAN DO WHATEVER THE HELL I WANT, then Java wins over ANYTHING GPL.
And, if you are going to doubt me without looking up the facts, consider who is on the JCP (www.jcp.org), ask yourself why Apache is on it.
I mean, I should expect your close-minded attitude, since many people here on slashdot slam Java because it isn't C/ASM.... but then again, I guess we could all make fun of you for making tools that you have to rebuild on each platform -- what a waste of time.
"But Java is slow!" So is X11 and e2fsck and format and dd.... It's the APP, you moron, not the language. Any REAL programmer would know that.
Sorry, this isn't meant to be a flame, but do some research before you post B$ as FACT.
Re:What do you mean GNU present??? (Score:2)
Whoa! Whoa! and Whoa! there buddy. Speaking of crackpots, you've been smoking from yours a little too heavily.
This post has nothing to do with the fine work the folks at IBM have done on Eclipse. That's old news.
This article is about the GNU components that have been released to allow Eclipse to run with all Free components.
I know it's trendy to bash RMS, and the Slashdot editors, but let's save that for when they are actually doing stupid stuff.
Re:Poster, get a fucking clue please! (Score:1)
Re:SWT binaries? (Score:2, Informative)
Yes, absolutely. Get ftp://sources.redhat.com/pub/rhug/swt-gcj-green-s
Run configure/make/make install, and you'll en up with lib-org-eclipse-swt.so.
People are also building for Win32 using gcj for Windows (or a cross compiler from Linux)
AG
Re:SWT binaries? (Score:5, Informative)
Yes.
SWT takes a middle ground between the extremes of AWT and Swing, and abandons a sacred cow of Sun's- the idea that the same binary must run on all platforms without any modifications. This attitude has really been an albatross around Java's neck and is the reason everyone thinks that Java applications have to be cheesy- because Sun demands that they must be equally cheesy everywhere!
AWT takes the approach that ALL widgets are drawn by the native layer. This isn't a bad idea, except that if no native widget is available (like a slider, or tree), AWT refuses to improvise one at the Java level. This is why there are no sliders or trees in AWT, even on platforms like Windows where native widgets for both are present, because there's some platform out there somewhere that doesn't have them. Maybe AIX or something, who knows. AWT is strictly lowest-common-denominator and that's why everyone hates it.
People bitched and moaned. So Sun went straight to the opposite extreme with Swing, which refuses to even consider the native widgets. Instead, it uses Java level methods to draw pictures of them to fool you. This means that Swing can offer you a "pluggable look and feel", so you can have Motif buttons on Windows, or "Metal" buttons on the Mac! Except nobody cares. Microsoft promptly kicked Swing in the nuts by introducing skins with XP, so it becomes obvious what is really Windows and what is pretending to look like Windows but can't keep up. And Swing suffers greatly from the second system effect- it's overengineered as hell. A Hello World in Swing gobbles up 20 MB of overhead- mostly classes loading and initializing themselves. In fact, Swing is why AWT is still alive. AWT sucks, but you can run a program that lasts for more than a couple minutes with it. Writing stable applications with Swing is a real art. (It is in AWT too, but only because Sun has pretty much left AWT flapping in the wind [sun.com] with minimal improvements, maintenance, or bug fixes. Since Swing came along, AWT has been treated like a red-headed stepchild by Sun.)
SWT is much more like AWT than Swing, except that it takes a practical middle ground- something Sun doesn't seem capable of doing at all! It offers you a nice set of native widgets. If a slider or a tree isn't available on some platform, they draw a picture of one for you. This might make sliders and trees look funny on platforms that lack sliders and trees, but you would expect things to look funny on those platforms. People using Windows (i.e. most of them) aren't bothered by any of this.
This sacrifices binary compatibility. Each platform has its own version of the SWT library. For example, there is a Windows specific swt.jar and a swt.dll that goes with it, and there is a Solaris version of swt.jar and a native swt.so library that it uses. Even though the libraries are implemented completely differently, the public interfaces are the same. So if you develop a program against the Windows version of the SWT library, you won't have any problem compiling against the Linux version. (Although I've heard that SWT blows on Linux, but that was a while ago and I don't know what the current state is.)
SWT doesn't abstract much away from you, unlike AWT, where you are separated from the low level GUI details by a leaky abstraction. In SWT you have to write the frigging event loop yourself! (Which is not a big deal- it's a while loop, usually two lines.) There are a few other gotchas, and you absolutely have to test a SWT program on all platforms you're releasing for, but in practical terms the same was always true for AWT because of the leakiness of its abstraction. SWT at least doesn't pretend that you don't have to worry about this stuff.
This means you have to compile and test a program three times before releasing it, once for Windows, once for Linux, once for Mac. This violates Sun's sacred cow of binary compatibility. But when you're releasing a Java application, you're going to make separate installers for each platform anyway, because you have to bundle a JVM for everybody. So it's not really a big deal, unless you're writing an applet- and applets went the way of the dodo long ago in no small part because of AWT and Swing!
With SWT, you can make really nice, professional looking programs. The layer between you and the OS is very thin (JNI). If your program looks silly or stupid, it's YOUR fault. When the user changes the skin in XP, your SWT programs will pick up the change right away. In fact, it isn't even obvious that you're not using C! You can write your stuff in Java and actually get away with it! So that's why I think SWT is the future (if there is any future left anymore) of Java on the client, and why I will be junking AWT/Swing completely when starting new projects.
For more info see the SWT FAQ. [eclipse.org] There is some GCJ and SWT [gnu.org] info available here. [ibm.com]
Re:I'm not that interested... (Score:1)
OpenBios [linux.de]
Story on