A more worthwhile perspective on GC, I think is this:
Compare doing simple string manipulations in C versus in Java.
In C it's hard work, but you can allocate intermediate arrays
statically and program their reuse. In Java, it's easy (so people tend
to use a lot of string joins etc), and has to
At 14:15 97/08/12, Philip Wadler wrote:
>> I think that Java might be slow, just because of this automatic garbage
>> collection.
>
>I can't let this chestnut go unchallenged. Let's not bandy about
>claims without evidence. GC is perfectly fine for building into phone
>switches (via Erlang) so
"Hans" == Hans Aberg <[EMAIL PROTECTED]> writes:
Hans> At 14:15 97/08/12, Philip Wadler wrote:
>>> I think that Java might be slow, just because of this
>>> automatic garbage collection.
>> I can't let this chestnut go unchallenged. Let's not bandy
>> about claims witho
> I think that Java might be slow, just because of this automatic garbage
> collection.
I can't let this chestnut go unchallenged. Let's not bandy about
claims without evidence. GC is perfectly fine for building into phone
switches (via Erlang) so it can't be all that slow. -- P
