I have not had many problems with recent versions of Limewire Crashing.

The problem I have is that its so slow that it often brings the whole system to a halt.

So slow in fact I have been looking for Non-Java based alternatives.

Non exist since OS X became the main Mac OS. All are Java.

Almost every Java app I have run has been a processor Hog. I have always attributed this to java being slow.

I read elsewhere here that the JRE in OSX is made By Apple and not SUN.

Where that was true in OS 9, in X the JRE is made by Sun for Apple and Apple distributes it.

A friend of mine just bought her first Mac. A G4 tower. Running Mac OS 10.3.2...

She tried to install Limewire 3.6.15. After installation every time she tried to run it it Unexpectedly quit.

I trashed her prefs, NO GO.
I Reinstalled Limewire, NO GO.
I removed all things Limewire, reinstalled, NO GO.

The only thing that worked was reinstalling the OS.

That worked for about a week. Where due to a move they hardly used the computer.

He had Limewire open then closed it.

They burned a CD, then went to open Limewire again. The same thing starting again.

It does not always crash immediately but it always does crash.

Other Java apps still work. Just not Limewire.

They did not install anything during that time period.

The only thing I can figure is going on is Limewire is corrupting something in the operating system. Since this is the only remedy that works.

Again, I have never had this problem so its frustrating that I can not fix this myself. The only difference between our computers is that hers is faster, with a combo drive. Other than that we are running the same version of the OS, Same version of Limewire.

Also, installing Limewire Beta version 3.8.8 does nothing to help.

Java isn't slow. It is Apple's UI implementation which lets Java look like slow.

Nope, Sun isn't responsible for the OSX JRE. Apple has licensed Suns Code and all OSX adaptations are made by Apple.

Open Console.app and tell us what it is saying when LimeWire crashes.

Java IS slow compared to other languages, not only on Macs.

Java works on all OSs, why can Java this and other can´t? Java is using a Virtual Machine which is translating it to your computer. Other languages work without this VM but are working only on one OS.

Java is slower because its needs time to translate the code with the VM.

Morgwen

That has been discussed N+1 times already. The Java 1.4.2 server VM is actually almost as fast as C++, in most fields like integer, floating-point & IO performance. It is supposed to be faster than C++ when creating objects.

Ask google for some benchmark results.

Java's VM is not an interpreter. The code is really compiled and repeated tasks don't require repeated compiling.

The speed difference of the Swing GUI compared to a GUI using standard Windows widgets is noticeable, of course. Java GUIs always seem to be a little slower reacting to mouse-clicks.

We can discuss this is again N+1 times, but the fact is that Java is slower compared to C++. ALMOST as fast don´t mean AS fast or did I miss anything... yes in some cases Java might be faster but the average speed is slower.

You can discuss this with my Prof.

Yes the code is compiled. But Java don´t know which OS you are using - the VM is translating the parts which are needed by your OS.

Java is slower than C++, and nothing what you tell can change this.

Morgwen

The original thesis you brought up is:
"Java IS slow compared to other languages, not only on Macs."

I argued that Java on Sun's JVM 1.4.2 is almost as fast as C++. And I'm sure I could dig up a GCC version to prove that Java is actually faster than C++.

(Please note the small difference in the semantics of "slow compared to" and "slower than")

Now look to which statement I replied:

So I used his word "slow" and not "slower". "Slow" is relative...

How does this version work? I guess not with a VM...

Morgwen

GCC or rather G++ has the reputation of notoriously creating slow and poorly optimized compiled code, while modern java VMs can profile and optimize the same code for different tasks in run-time.

Here is an article from somebody who did the right tests to prove that Java is faster than C++
http://www.kano.net/javabench/index
http://www.kano.net/javabench/data

This is another interesting article on the same topic (and a little less biased) although a little older:
http://www.idiom.com/~zilla/Computer...benchmark.html

It wasn't my intention to start a flame war. I'm just tired of seeing people saying Java is slow when it's actually Apples fault and inability to implement a proper AWT/Swing<->Native UI interface.

_All_ (!!!) performance issues with Java on OSX have someting to do with the UI. Some benchmarks show that Apples new Cocoa based UI for Java 1.4 is in some cases 1000 times slower that it was in Java 1.3 which has a Carbon based UI.

Or take a look at this:
http://rsb.info.nih.gov/plasma2/

I get 110fps on my 2x2GHz G5 with Java 1.4.2DP2.

Some good examples that Java isn't slow are Acquisition, AqLite or Fern 0.1. Fern was my own Cocoa/Java UI wrapper for the LimeWire core and the UI of Acquisition/AqLite is written in ObjC. Most of the Acquisition/AqLite users even don't know that their clients are driven by 50k lines of Java and maybe 10k lines of ObjC code.

Who has flamed here? Did I miss anything?

And I said that not only Mac users say that Java is slow, and we discussed about that - did you follow the discussion?

Morgwen