Subject: Re: Re[2]: [linux-audio-dev] LAAGA proposal, part ??
From: Jay Ts (jay_AT_toltec.metran.cx)
Date: Mon Jun 11 2001 - 05:19:49 EEST
Greg Turpin wrote:
> According to the javadocs:
>
> "Calling the gc method suggests that the Java
> Virtual Machine expend effort toward recycling
> unused objects in order to make the memory they
> currently occupy available for quick reuse. When
> control returns from the method call, the Java Virtual
> Machine has made a best effort to reclaim space
> from all discarded objects."
>
> Now, by no means am I suggesting that anyone use
> Java for audio. If you let java decided when to run
> garbage collection - you'll run out of memory. If you
> decide to call System.gc(), your application will suffer
> a MAJOR performance penalty.
Thanks Greg, that information is about what I thought
things were like, and I agree with what you wrote
above. (I didn't think enough before posting my
first message, but judging from the responses, it
looks like I didn't mess up too badly!)
I think C is still the best language by far to
use for most "serious" audio work, including just
about any realtime apps. But to be fair, Java
may come in handy for some developers, for *some*
purposes. Like doing SysEx MIDI dumps, for example.
(E-mu has a Java utility for downloading OS updates
into their synth modules, and they were able to
support both the Mac and Windows platforms with
the same code. Sometime I should see if I can
get it to run on Linux too! They didn't say
it wouldn't work...)
- Jay Ts
This archive was generated by hypermail 2b28 : Mon Jun 11 2001 - 07:13:26 EEST