4 ms·

A huge number of Java apps built for enterprises or corporations are Windows-native as well. Either compiled down to a .exe, installed via a Windows-native Inst

by danudey 12y ago

A huge number of Java apps built for enterprises or corporations are Windows-native as well. Either compiled down to a .exe, installed via a Windows-native Installshield installer, built using Windows-only native-library code, or designed assuming Windows (e.g. referencing C:\ directly in the code). And honestly, paying extra in 1998 to have the contractor write a Java app to support multiple operating systems would have been a huge waste of money, since there weren't really any other platforms that businesses used (or at least, not these businesses). The real 'they deserve everything they get' is that they didn't start this process sooner. The IT departments should have gotten their hands on the Vista DVD, tested their custom software, seen which way the wind was blowing, and started a project to modernize their systems. They could have spread the project (and cost) out over seven years, but instead they didn't start the process until it was too late to avoid huge expenses. It's exactly the same as people who didn't take Y2K seriously until September 1999, and then said 'Okay we need to update all of our things, can we have that done by November just to make sure?'

tormeh 12y ago
>A huge number of Java apps built for enterprises or corporations are Windows-native as well. Either compiled down to a .exe, installed via a Windows-native Installshield installer, built using Windows-only native-library code, or designed assuming Windows (e.g. referencing C:\ directly in the code). That reads like a catalogue of worst practices. It's possible to make Java apps really portable by doing absolutely nothing. You compile Java code to .class format, and then you are done. You would probably want to include your own JVM and a shortcut or bash file invoking it on the bytecode, but the point is it's actually more effort to make them non-portable.

by danudey 12y ago

tormeh 12y ago

>A huge number of Java apps built for enterprises or corporations are Windows-native as well. Either compiled down to a .exe, installed via a Windows-native Installshield installer, built using Windows-only native-library code, or designed assuming Windows (e.g. referencing C:\ directly in the code). That reads like a catalogue of worst practices. It's possible to make Java apps really portable by doing absolutely nothing. You compile Java code to .class format, and then you are done. You would probably want to include your own JVM and a shortcut or bash file invoking it on the bytecode, but the point is it's actually more effort to make them non-portable.