How is java programming different in 64-bit?

2 thoughts on “How is java programming different in 64-bit?”

1. it shouldn’t be any different. java acts as a link between your program and the operating system. java programs only see the java virtual machine, not the actual system, and there’s no such thing as a “32bit” java program and a “64bit” java program

   Log in to Reply

2. The code you write is handed off to an interface we call the Java Virtual Machine. The Sun engineers wrote an engine that invokes the capabilities of the platform your code is running. You write code to the JVM. The Sun engineers have optimized the JVM for the various platforms. For instance, there is the Windows Look-And-Feel, but you can not invoke that L&F on a Mac or Linux (not without a lot of extra effort anyway).

   So, in-as-far-as 64-bit, the only thing different is the plug-in. And to have true 64-bit you have linked the Java1.6_update16 JRE. I/O does run faster. Some java features are missing. java6 includes the native Desktop and SystemTray. With that Desktop API you can fire the default browser or word processor of the OS. Somebody forgot to include Desktop API with the 64-bit plug-in. I haven’t tried the SystemTray (Taskbar).

   In a similar gripe: JavaFX. Mac and Windows have a default video player. Linux does not. The Linux JavaFX doesn’t have video capabilities, only some of the core features of JavaFX. Sun and Adobe were working on an .svg graphics translator to include vector art with JavaFX code. Microsoft has their own idea about vector graphics for web plug-ins and is incompatible. In fact, the MS vector graphics format is when Adobe split off from a joint committee with Microsoft. But, back to my gripe. JavaFX in Linux does not include the .svg translator.

   In a word, 64-bit is only 90% complete but I hope you understand now that it is the JRE optimized as a Virtual ideal.

   Log in to Reply