Code it again!!
 

Code the whole thing again in C!
This client is completely useless on old hardware!

Err...how come I dont share your opinion?
You are saying it so easy: "Hey! Throw away the code you've been working on for years and just simply code a new LimeWire."

No problem :rolleyes:

the re-coding process
 

well.. Throwing away your "fantastic" code would be somewhat silly,
but many of the bugs that currently resides in it, are java-bugs.

so subsequently; many of the bugs will be sorted out in time, as java will (hopefully) learn to walk the same way that the other languages walk.

but in the mean time, you should at least consider doing a basic c-version as a professional server or something like that. The java client simply isn't stable enough (and it won't be in a long time) for 24/7 servers. It isn't even stable enough to be a client, and that should mean something.

It's not that I don't respect the work that has been put into this project, it's truly amazing to see it, knowing it's all java. But java is still a toy, and it will be for many year to come.

The portability issues can be overcome in other ways than doing all-java-software. At least that's my opinion.

But the limewire client is a truly amazing piece of software, even though it basically "does not work."

keep up the good work! and let's hope sun keeps up theirs!

Re: the re-coding process
 

Huh? Are you using the same program as the rest of the world?

to follow it up..
 

I liked Limewire for it's ease of use..
I didn't like the part about the spyware and the
freezing and of the lack of ability to resume (it does a couple of times a day, but that counts as maybe 10% of the times), but what REALLY-REALLY-REALLY annoys me:

Limewire-nodes counts as about 10% of the network, maybe less. Roughly 50% of the users use Morpheus. The guys using Limewire are almost exclusivly the worst sharers (that's my not very solidly based assumption). *Limewire "prefers" other limewire-nodes. That makes the limewire-"community" a subculture on the gnutella network. If you are lucky enough to get a morpheus node on your connections-list, you will see that it (usually) has a tenfold as many hosts attached to it countary to the limewire peers.

Maybe that is a feature you should remove (??)
Think of it guys! If all the limewire nodes just prefers themselves, the limewire community (as small as it is) will come to be a subculture, thus sharing files with everybody but just getting hits from themselves. The only time you get real results, is when you find a morpheus supernode with 1000 hosts or something like that.

I recently tried qtella on my linux system and my hits quadruppled on the long-hard-to-find-ones and
increased with a 40-50 fold on the generic searches.... Then I suddenly realized how crappy limewire really is. It's nice in consept and theory but it just don't scale up as a c++ client will.

Sorry, limewire-team. You've done an amazing job, but I'm afraid my limewire client will remain a silly toy for my win32 system. the thought of buying your program, honestly never crossed my mind, but as time goes by, that offer seems somewhat stupid to me.

Re: to follow it up..
 

That is not and does not represent my experience... my worst experiences in searching are almost exclusively when I have a large number of Morpheus connections. That includes Limewire and a half dozen other clients I use.

Perhaps this has more to do with Limewire not flooding the net with requests for extended periods of time ... some clients do not adhere to this pricipal and ignore the fact that doing this is bad for the entire Gnutella community not to mention selfish. Yes, I believe Limewire can be improved but the Java approach, I believe, is simply an attempt to service mutliple platforms in the easiest way possible.

flooding, selfishness and other acts of cruelty are not good.
That I understand and respect. The question is: does it really bother me?

I have a 1MB internet hookup, and maybe that is somewhat faster than the average user, but even when I get a peak of query's passing through my node, I can't say that I feel it too high price to pay for getting more and better results.

Distributed net's are kinda like how the brain works, except it's bidirectional. The brain has no HLT instructions, it's allways working. The same goes for the gnutella net. It will allways be some kind of activity on it. The more activity, the more information will be passed. The more information, the more files.

Do we really want retards sitting on modem-connections to slow us down? Limewire fixes this by adjusting their gnutella-connections to a proper level (as apposed to f.eks. qtella), but why allow them on in the first place?

when the thickens plot, the plot thickens. if you can't stand a 40-50 KB/s load just to be connected, you shouldn't use the gnutella network. I for one, do not like people with modem connections leeching files from me. It's not the leeching I disapprove of, but the slow connections. Maybe it's time the gnutella community got segregated into two different nets (?)

One for limewire users on dial-ups,
and one for users on hard-lines. Über-nodes. :)

As for the java-approach. As said before: I like the concept in theory. In practise it just won't add up. Even though an OS would be ultra-portable if run in a javavm, nobody bothers. Even though an entire office-solution would be pretty darn cold in java, it won't add up. I could go on and on, but my point is :

YOU ALLREADY SERVE DIFFERENT PACKETS TO DIFFERENT OS' ANYWAYS? Why the hassle?! If you can't port your own code, it's a fat chance in *e*l that you'll end up with a vital java-client.

At least that's my point of view.. :)

C sucks. C++ sucks worse.

Try tuning your machine. I've got a 166Mhz thats humming....
www.tweaktown.com has some nice suggestions. check out "guides"

also, this guy is good! http://www.blackviper.com/WinXP/servicecfg.htm

Some of the stuff about services applies to NT also.

oh yeah, in addition to tweaking your machine....

you CAN override the default (6) number of connections Limewire allows. Modify the Java properties file with notepad- attribute is "keep alive". I have mine set to 19....

(GUI edits enforce rules only allowing you max 6 connections 'so you don't create too much network traffic'. Direct edit with notepad bypasses GUI edit.

c is the closest thing to assembly code around, and it rocks.
c++ is little slower, but it's objects kick ***.

i've got a 133mhz dell xpi latitude running linux and qtella perfectly. and my 1,1ghz workstation runs like a dream under linux, still it's really annoying to use both win32 AND javavm together on one app (limewire), as both of them are notorious resource-hogs. as for the win32 system and optimizing, thanks for the tip, but i do not think i will bother doing win32 no more.

the properties file, i am quite aware of, overrides the gui stuff.
but still I find it an odd number (6) to pick for a 1MB sdl connection. And that is more a comment to the limewire team than to you. for fun you may want to experiment with the ttl settings, just to be an ****. ;)


quote:
C sucks. C++ sucks worse.
Try tuning your machine. I've got a 166Mhz thats humming....
you CAN override the default (6) number of connections Limewire allows. Modify the Java properties file with notepad- attribute is "keep alive". I have mine set to 19....