have used on a friends mac and was easy to use, layout was nicely done, and no complications with connection or hosts and sources.
i think there was a thread like this on the acq forums. the answer? no.
nsap @ filesharingtalk.com
well sense some windows p2p apps dont go to MAC. I guess us Windows users desereve not to get this.
meh
even if it was the greatest app of all time, it's still just another gnutella client--aren't there enough of those for windows already?
player integrations, recommendations, all useless fluff that gets in the way of the applications real function, which i would say is to search for and download files (of course if you want a bloated gnutella app that has most of that crap, shareaza fits the bill)
i found that thread... there is no acq for pc because there is no carbon for pc. and since acq is written in carbon... you won't get acq anytime soon either.
nsap @ filesharingtalk.com
Well, it is availble. Commonly known as LimeWire :). They really are pretty similar.
and now limewire is also clean , with no spyware or adware inside it
And I can't tell you how happy I was to here/read that.nd now limewire is also clean , with no spyware or adware inside it
It's truly a step in the right direction, even if I don't use the Gnutella network anyway.
You can't triple stamp a double stamp.
can i have some of the pot you're smoking? since when did limewire pull that nasty adware out?Originally Posted by mybackhurts
either way, limewire is java, and java is, for the most part, terribly slow. acq is carbon, and is much faster.
nsap @ filesharingtalk.com
Well there is CleanLimWire. Also Java is not slow, Java GUI's are sluggish, the code is able to perform as well as anything, the GUI just doesn't have the instant response many windows users are used to (Microsoft put the GUI directly into the win32 Kernel)Originally Posted by isus
DILLIGAF
damn spam threads! This guy already made 3 different ones earlier today!!
Ban his ass
Java code is interpreted at runtime, and in some cases, is measurably slower than code compiled to "native" instructions. While the Java graphical user interface toolkit, Swing, is well-organized and exhibits a fair representation of model-view-controller architecture, compared to "native" user interfaces, it is perceivably slower and consumes a much greater amount of memory resources.
The good news is, the remarkable folks at Sun Microsystems are constantly working to improve the performance of Java. In some cases, Java code supposedly competes effectively in performance tests against "native" code.
It's actually compiled at runtime. The difference is subtle but important. While an interpreter would interpret the same function again and again whenever it is called, Java compiles and caches it. That's why the difference between java and native code can become very small for some applications.Originally Posted by smokingbevel
The larger part of Acquisition is LimeWire's java core, so the only noticeable difference in speed can be LimeWire's Swing GUI vs. Acquisitions Carbon GUI. If you minimize the LimeWire window, the difference is zero.Originally Posted by isus
Bookmarks