No longer are you restricted to running Java applets and programs within your favorite browser. The beauty of MRJ is that it makes running Java applets and programs a transparent, built-in function of your Mac. My recommendation is that you have at least 32MB of RAM - MRJ is a memory hog, and will bog down or refuse to load applets under even the lightest Java load, even in 16MB of RAM. (The 68K version, currently in its fourth beta, lists the same requirements, and no less than a 68030 processor.) Since MRJ runs in system memory (as opposed to running within another application's memory partition), Apple strongly recommends having 16 MB of RAM to comfortably run MRJ and other Internet apps concurrently. MRJ asks for a minimal configuration of System 7.5, 4-6 MB of hard disk space, and at least 8 MB of RAM. If OpenDoc is present, Applet Viewer Stationery (used for embedding Java applets within other Live Objects, such as Cyberdog documents) is also installed. Like most Apple products, MRJ installs in a snap, dropping Java class libraries within your System Folder and the Apple Applet Runner program, along with Java applet examples, into its own folder. While the potential uses for MRJ are appealing - consider the future bundling of Marimba's Castanet Tuner with MRJ (see Webintosh's First Looks page) - my examination of MRJ focuses primarily on how it enhances the function and interactivity of the average Joe's (or Jane's) Web browsing experience.
#JAVA FOR POWERPC MAC SOFTWARE#
While significantly more sound than its beta predecessors, MRJ still feels rough around the edges compared to the Java software included with or built into other popular Internet programs.
#JAVA FOR POWERPC MAC MAC OS#
Processor: PowerPC Only (68K forthcoming)Īfter several wobbly beta releases, Apple recently introduced version 1.0 of Mac OS Runtime for Java (MRJ). Very slow RAM-hungry quirky and inconsistent performance. System-level Java support makes Java applets/programs double-clickable reliable performer cheap. MRJ won't win any contests for speed or comprehensive support of Java, but neither will it crash your machine every time you use it with your favorite browser. Implementing a Java Virtual Machine is an admittedly tricky business, but Apple has done pretty good on its first try with Mac OS Runtime for Java. If you work for Apple and you think you might be able to help with this, please contact me.The Mac Observer Express Daily Newsletter If your organization would be interested in joining such a joint request to Apple to support JSE 6 on (at least) all supported Leopard platforms, please let me know. It is possible that Apple might pay more attention if a number of their customers made a joint request. My organization (MIT) has submitted a bug report to Apple about this. I'm told that Sun has both 32-bit and 64-bit JSE 6 JVMs for Windows, for Linux, and for Solaris.
If this remains true in Apple's final release of JSE 6, then the next major release of the Mac SAPgui won't run on any MacOS X prior to Leopard and won't run on PowerPC or 32-bit Intel based Macs even with Leopard.
It is likely that by the time of SAP's next major release of the Java SAPgui, Apple will support JSE 6 and the Mac SAPgui will require it.Ĭurrently Apple's implementation of JSE 6 requires a 64-bit Intel processor running Leopard. Hence, the Mac version of the Java SAPgui doesn't yet use JSE 6, even though the Java SAPgui on other platforms does use JSE 6. Apple has a developers' preview version JSE 6, but they don't yet support it.
0 kommentar(er)
