New Desktop Features Of Next Java

bonch writes "Sun has posted the new desktop features of the next Java, codename Mustang. Improvements to Swing look and feel, OpenGL 2D renderer performance, AWT features such as the ability to add a tray/panel icon, and improved deployment capabilities."

Comments

Re:Additional items

[Anonymous Coward]

For those of you who want a better alternative to slashdot which isn't full of errors, redundancy, and trolls: http://news.google.com/nwshp?topic=t

I couldn't find the discussion section on Google News. Can you show me where it is, please? I want to discuss news stories, not just read them.

JAVA - the little train that could

[IAmTheDave]

This is downright stupid. How long, exactly, has JAVA been in existance? YEARS. It should never have taken such a mainstream language so many many years to have such basic features in the UI package. We're supposed to ooh and aah over this like it's exciting, breaking, important news. This is JAVA catching up to 10 years of simply horrible UI design (and other features.)

64-bit pointers

[tepples]

I guess the VM could use 64-bit pointers internally, but as you can't access memory directly in Java I don't know how the programmer would ever be able to tell.

Exactly. So why is Sun dragging its feet on porting its virtual machine for the Java language to the AMD64 platform?

Re:Additional items

[Jonboy X]

Wow, if only there were a moderation "Doesn't know what the hell he's talking about"...

1) The ability to allocate more memory space to Java apps.

From the command line, run "java -X". Note the -Xmx and -Xms options to allow you to control initial and maximum heap space. These options have been around for years.

2) 64 bit support.

Ever heard of the SPARC processor? You know, the one Sun produces, one of the first mass-market 64-bit platforms available?

Assuming you're talking about AMD64, there's already a JVM that supports it. Linux-only at the moment, but if you insist on using platforms that suck, there're already AMD64 Windows JRE release candidates up too.

3) Ability to/Easier implementation of hardware specific calls to speed calculations.

Now you're just missing the point entirely. One of the major goals of Java is that the same compiled binary can run on any machine with a compliant JVM written for it. When you start making calls to specific hardware, you lose that. Besides, if you *do* want to sacrifice the platform portability of your program, you can always just write a JNI module for it, but then I suppose you don't have a clue about that one either...