Linked by theuserbl on Sun 10th Jul 2011 18:48 UTC
Java "After an initial round of testing we've declared build 147 to be the first Release Candidate of JDK 7. There are only thirteen changes in this build. Over half of them are administrivial updates that don't affect the actual code; the remainder are true showstoppers, including several hard VM crashes and a JIT correctness bug identified by an Eclipse unit test. If no new showstopper issues are reported, and if JSR 336 and the component JSRs pass their Final Approval Ballots in the JCP, then this will be the GA build for release later this month per the schedule posted back in January."
Thread beginning with comment 480230
To read all comments associated with this story, please click here.
great
by andih on Sun 10th Jul 2011 22:36 UTC
andih
Member since:
2010-03-27

thats great!
if they just could keep java away from the web...

Reply Score: -2

RE: great
by ebasconp on Mon 11th Jul 2011 00:06 in reply to "great"
ebasconp Member since:
2006-05-09

Several years ago, the mediocre Java performance and the lack of good widget libraries marked Java as slow and memory hungry when the first Java applets appeared, most of them based on AWT or 'homemade' widget libraries.

Sadly, these days the myth of Java being slow and memory hungry still remain.

I think if you could compare two current applications running inside the webbrowser, one made with the latest Flash release and the other one using JavaFX running on top of the latest JVMs, the performance would be comparable or, probably (I'm just speculating here) would be better in the Java side.

Reply Parent Score: 2

RE[2]: great
by frytvm on Mon 11th Jul 2011 01:19 in reply to "RE: great"
frytvm Member since:
2009-11-11

Yeah, Java has excellent numeric performance, there's no way flash could compare; to be fair, ActionScript is not really designed for performance the same way Java is.

On the other hand, startup time and Swing performance have been constantly disappointing for normal desktop users: even on my relatively new laptop, IDEA's menus somehow feel slow and unresponsive to pop up compared to any native program.

With the JVM being such an attractive target for alternative language implementations (hopefully getting tailcalls _someday_), one can only hope Oracle can fix-up these final minor flaws with the new JVM, and who knows what the merger of also-Oracle-owned JRockit's techniques can further do for performance.

Reply Parent Score: 3

RE[2]: great
by WorknMan on Mon 11th Jul 2011 02:44 in reply to "RE: great"
WorknMan Member since:
2005-11-13

I think if you could compare two current applications running inside the webbrowser, one made with the latest Flash release and the other one using JavaFX running on top of the latest JVMs, the performance would be comparable or, probably (I'm just speculating here) would be better in the Java side.


Well, given how bad Flash performance is on most mobile/tablet devices (and even some desktops), comparing Java and Flash performance is like comparing the shit I took last night with the shit I took this morning. Either way, it's still shit.

At work, we have Java apps running on servers inside of tomcat/resin instances, and we're constantly having to restart them because of OutOfMemory errors and cpu spikes. For some of them, we have to restart them once or twice a day via crontab, because the architects can't figure out WTF is causing them to wig out and swallow up RAM/CPU resources like a Hoover. Of course, I did not write these apps, so who knows how well written they are, but it seems like Java is a hog no matter what environment it runs in.

Edited 2011-07-11 02:50 UTC

Reply Parent Score: 0