This is an opinion from someone who has worked extensively in both Java and
C++....if the application requires high performance(say auto routing, hint,
hint) Java will be a factor of 3-5X slower than C++. And it will be a
memory pig, on most JVMs the "Hello World" app will consume 10MB+ just on
it's own. An app the size of PCB will likely consume 60-100MB. And when
the garbage collection kicks in at seemingly random times...look out.
Java would just be a bad solution all around for PCB, not to mention the
extensive rewrite to an existing functional codebase.
Suggest finding a cross platform toolkit. Also suggest finding something so
that it can easily be compiled/installed on Windows. The only reason I keep
a Linux box around here is to run gSchem and PCB. I know, I've installed
PCB on my Windows box here with Cygwin,X11, etc. But most users don't or
can't go to those type of pains.
From: Bob Paddock <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: gEDA-user: Free Dog meeting report: Notes on the topics we
discussed
Date: Tue, 20 Sep 2005 06:03:29 -0400
On Monday 19 September 2005 05:57 pm, Olgierd Eysymontt wrote:
> Why use a native toolkit ? why not use Java, works great,
That has not been my experience with Java. I just hate the thoughts
of dealing with anything involving Java. Also Java is a language not a
tool
kit.
> it's fast and
> easy to mantain (lots more than c or c++), runs not only in Linux and
> Windows but all platforms and it's very easy to create complex
> interfaces.
Exactly. No one wants complex interfaces, we want ease of use.
