Slashdot Mirror

← Back to Stories (view on slashdot.org)

IBM Releases Fastest SDK For Java 6

Posted by kdawson on from the early-start dept.

IndioMan writes "IBM is releasing an SDK for Java 6 and is sponsoring an Early Release Program to gather feedback from the Java community. Product binaries and documentation are available for Linux on x86 and 64-bit AMD, and AIX for PPC for 32- and 64-bit systems. In addition to supporting the Java SE 6 Platform specification, IBM's SDK also focuses on platform stability, performance, and diagnostics. It's tops on every benchmark."

6 of 117 comments (clear)

  1. x86_64 plugin = Heros by baptiste · · Score: 4, Interesting

    If they include a x86_64 browser plugin they'll be heros. It's 2007 and Sun still refuses to release a 64-bit browser JRE plugin because..... why?

    --
    Top Most Bizarre/Disturbing Error Messages
    1. Re:x86_64 plugin = Heros by bcrowell · · Score: 4, Interesting

      By March, 100% of Java will be available under GPL, right? So at that point, I would think that anybody who has the skills and time will be able to clean up any code that's not 64-bit clean, and compile a 64-bit browser plugin. I'm looking forward to seeing some really good things happen in OSS with Java, now that all the licensing impediments are going away.

      --
      Find free books.
  2. Re:The Fastest JDK? by badfish99 · · Score: 2, Interesting

    It's certainly possible for Java code to run fast, once it's been through the just-in-time compiler, i.e. once it has been compiled to native code. That would surely be true for any language. But that means that you have to load up the whole of the compiler into memory in order to run your program. This is fine on a server, so long as you don't care about the cost of memory. It's a disaster on a client machine.

  3. Re:The Fastest JDK? by jrumney · · Score: 2, Interesting

    Are your "write once, run anywhere" applications using internal APIs, or are they relying on bugs in the 1.3 class libraries to run? Personally I've only ever come across code that DOESN'T run properly on 1.3, due to bugs introduced between 1.2 and 1.3, and fixed in 1.4.

  4. Bindings by ChunderDownunder · · Score: 2, Interesting
    This isn't to prove, per se, that the fox toolkit is any faster than gtk but that the corresponding translation to Java is.

    The SWT binding directly accesses gtk through JNI. This may have suited IBMs purposes of accessing gtk through the SWT API but might not be the most optimal binding of gtk to Java.

    The java-gnome project produces java bindings for gtk. They are in the process of being re-written from scratch using 2007 best practice JNI binding techniques. I suspect that an SWT implementation using this approach would far outperform the current offering. Maintenance would be far simpler too: no native code in the SWT layer!

  5. Where are the sources ? by mritunjai · · Score: 2, Interesting


    SUN has released the sources to it's compiler and JDK.

    IBM where are thou the benefactor and promoter of Open Source ? Show us the GPL sources to your JDK and compiler!

    --
    - mritunjai