> > anyway.
>
> But then, whether Java is good for something depends on how speed
> dependent the task is. For example, Java is probably quite fine for a
> Freenet node reference implementation, but it is probably not adequate
> when you have a Freenet node with a big SDSL pipe and a 2+ gigabyte
> datastore which receives a very large number of requests and inserts
> per unit time.
Ah, but I disagree. I think Java is quite capable of filling just such a
pipe. The size of the datastore is irrelevant. In fact, I know it,
having run a streaming MP3 server on a fast-ethernet link with a
client-load of up to 150 users. And this wasn't a performance tuned
shout-server, but an MP3 server running on the Gamora framework.
> As for classpaths, Java implementations should bother to look in the
> working directory for classes. That would reduce the constant
> frobbing of environment variables.
Unix doesn't 'bother to look in the current directory' for executables
either. You have to add '.' to your path. Just like any competant system
manager would include '.' in the global classpath.
> > Hate to start a language war, but I just hate anti-java bigots.
>
> I am not an anti-Java bigot. I just had some gripes with Java. Java
> is fine for doing stuff like reference implementations and other stuff
> which do not need very high performance.
Well, opinions are like assholes (everybody has one).
Scott
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20000730/e958024b/attachment.pgp>
