On Wednesday, 03/20/2013 at 10:12 EDT, "Chase, John" <[email protected]> wrote: > Wasn't the design philosophy behind Java, "Write once, run anywhere"? What > went wrong?
What everyone discovered was that: (a) New releases of the Java have a tendency to break existing applications that live near the edge of the spec. (b) Too many applications seem to live near the edge. (c) Bright and shiny Java extensions are helpful AND habit-forming. (d) You need more than a patch to break the habit. (e) Organizations want to speed up cycle time and reduce development costs. Therefore they want to ship the java they tested with so that they control the content and don't have to re-test or re-certify each level of Java. (f) While Java is the IT version of Esperanto, it's still just a programming language that uses a run-time library. (g) It takes a run-time library a long time to become dependably stable (LE, anyone?) (h) Ah, so THAT'S what Grandma meant by "Too many cooks spoil the broth!". So began as a revolution in program development ended up as "Write once, regret everywhere." There oughtta be an international "Java Proliferation Treaty". Alan Altmark Senior Managing z/VM and Linux Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 [email protected] IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
