Slashdot Mirror

← Back to Stories (view on slashdot.org)

Quest For "Unbreakable Java" Unites ABAP & Java

Posted by Hemos on from the its-a-festivus-miracle dept.

jg21 writes "Writing an article about "A Java Server That Never Goes Down" is pure hubris, but a German developer who says he's been "eating, sleeping, and drinking Java" for 8 years doesn't seem to care and his article brings to light the aspects of VM we rarely think of as he introduces "user isolation" and tells about some interesting work SAP in Germany is doing in that area, merging the Java and the ABAP worlds."

2 of 198 comments (clear)

  1. Shared memory w/ processes is no better by Anonymous Coward · · Score: 3, Insightful
    than shared memory with threads. Threads are basically just processes that share the same memory. And it's the shared part that makes resistance to errors or error recovery so problematic.

    If a process crashes then all memory that the process has access to is suspect. If that's all the jvm contexts then they're all suspect.

  2. Re:Step on those Beans! by OwnedByTwoCats · · Score: 4, Insightful

    I have programmed professionally in at least 8 languages, including C, C++, perl, and PL-SQL, and have worked in several others in academic or limited settings.

    I have been doing Java since 2000, coming from C++.

    Java isn't bad. It is complete; it has a threading model with appropriate concurrency controls. It isn't that different from other imperitive object-oriented languages. It has automatic garbage collection. After startup, on our applications, the performance difference with C++ is negligible, and what we save with automatic GC is quite bankable.

    My employer used two strengths of Java to justify the move from C++: platform independence, and garbage collection.

    I don't know what jbich wants to see in a language.