🚀 go-pugleaf

In article <ejalbert-3FBDD1.13140019102000@nntp.stanford.edu>, Eric 
Albert <ejalbert@stanford.edu> wrote:


> The speed isn't really Metrowerks' fault, or that of the Java team at 
> Apple.  Sun's debugging API reflects Sun's belief that TCP/IP is the 
> best solution for everything, which isn't really always the case.

Well, debugging Java on Windows is fast and Microsoft isn't tooting Java 
as the official programming language of it's new operating system like 
Apple is.  Context switching doesn't seem like an adequate reason for 
the slowness.  We're talking MINUTES to display all the member variables 
of "this".  A context switch on a PowerPC is faster than a context 
switch on an Intel machine.

I put the blame squarely on Metrowerks and Apple's shoulders.  If Apple 
wants folks to use Java on their next OS, they better make sure they can 
use it the current one.  If Metrowerks wants to charge hundreds of 
dollars for a Java development environment, they better make sure it's 
usable.  Sun is just a contractor in this development effort.


I'm a java newbie but an old Mac development hand.  Yeah, I can use 
macsbug and println but I'm sure not going to be able to convince my 
co-workers that the Mac is a cool machine to develop Java on.  And that 
should be Apple and Metrowerk's aim.

Bob
bgulian@staff.iwon.com