> "Matthew" == Matthew Pocock <[EMAIL PROTECTED]> writes:
>> In short, using all the memory you possibly can, but without
>> actually crashing the JVM is fairly hard in Java. Or, if I am
>> more honest, I never found a good way of doing it. Perhaps
>> someone else has. Cheers
>> Ph
On Tue, Feb 11, 2003 at 10:48:05AM +, Phillip Lord wrote:
>
> In short, using all the memory you possibly can, but without actually
> crashing the JVM is fairly hard in Java. Or, if I am more honest, I
> never found a good way of doing it. Perhaps someone else has.
To be honest, I'd say that
In short, using all the memory you possibly can, but without actually
crashing the JVM is fairly hard in Java. Or, if I am more honest, I
never found a good way of doing it. Perhaps someone else has.
Cheers
Phil
___
Biojava-l mailing list - [EMAIL PRO
> "Ewan" == Ewan Birney <[EMAIL PROTECTED]> writes:
Ewan> On Mon, 10 Feb 2003, Bill Torcaso wrote:
>> Ewan,
>>
>> As an old-time C programmer who never learned C++ but is very
>> happy with Java, I have a question about your comment, "my
>> algorithms try to use all the memory of
On Mon, 10 Feb 2003, Bill Torcaso wrote:
>
> Ewan,
>
> As an old-time C programmer who never learned C++ but is very happy with
> Java, I have a question about your comment, "my algorithms try to use
> all the memory of the machine". What do you do about malloc() and
> free()? It seems to me t
Ewan,
As an old-time C programmer who never learned C++ but is very happy with Java, I have
a question about your comment, "my algorithms try to use all the memory of the
machine". What do you do about malloc() and free()? It seems to me that the most
significant part of the "contract" betwe
Ewan> For guys who do run Java as part of their production code in
Ewan> bioinformatics,
Ewan> (a) do you have versioning problems over time?
Versioning with Java is a pain in the ass. We seem to get repeated
problems with different versions both in terms of point releases, and
versions o
Ewan Birney wrote:
On Mon, 10 Feb 2003, Simon Brocklehurst wrote:
Ewan Birney wrote:
True. Probably more of my reluctance is the relearning curve. But I often
my algorithms try to use all the memory of the machine, and if I start
running some extra overhead I wont be happy...
... but, yes, it
On Sun, Feb 09, 2003 at 09:24:07PM +, Ewan Birney wrote:
>
>
> I know... this is a troll but it sort of resonates with me about the
> way Java development works - people have to fix on a JVM version to get
> real like-a-rock stability and work about bugs in that release, and
> Java is ju
On Mon, 10 Feb 2003, Simon Brocklehurst wrote:
> Ewan Birney wrote:
>
> Ewan,
>
> The issues in that memo are real. Are those *really* the reasons for
> your reluctance to move to Java? Are you sure it's not more of a "not
> wanting to start all over again" kind of learning issue?
>
> I rem
Ewan Birney wrote:
Ewan,
The issues in that memo are real. Are those *really* the reasons for
your reluctance to move to Java? Are you sure it's not more of a "not
wanting to start all over again" kind of learning issue?
I remember very well when I switched from C to Java in 1997, it was
pr
On Sun, Feb 09, 2003 at 04:56:28PM -0500, Dave Keller wrote:
>
> >This is why I think i have alot of reluctance to move to Java; C is by far
> >my prefered strongly-typed, "non-scripting" language. But I am a
> >dinosaur...
> >
> >
> Nothing wrong with that, C is an excellent language and there i
Hi Ewan,
I've never really noticed a problem with settling on a JVM in terms of
bugs. The only problem with settling on a particular JVM for us has been
wishing we could use that really cool feature from the latest release.
We have done various upgrades of JVMs and they seem to be realtively
painl
I know... this is a troll but it sort of resonates with me about the
way Java development works - people have to fix on a JVM version to get
real like-a-rock stability and work about bugs in that release, and
Java is just dreadful in resource management (in particular memory
footprint) meani
14 matches
Mail list logo
