On Sun, 2002-01-20 at 05:24, John Wm. Wicks wrote:
> Yes but Java has it's own limitations, performance is still it's weakest > link. I've used a Java based IDE called Eclipse and it's unacceptably > slow on my Pentium 450. Since the primary role of this interface is > filtering and parsing I'd hate to see it bogged down by the overhead of > a completely Java implementation.Swing is still the slowest part of java I believe, so comparing a heavyweight gui app to a file parsing library isn't fair. Along with that, j2se 1.4 brings noticable performance improvements.
See also :
http://www.javaworld.com/javaworld/jw-02-1998/jw-02-jperf.html
(this is quite old - things have improved since then)
We're using java for our internal parsing needs, and it's very fast indeed. (our localisation filters are implemented using javacc) and there's all the gains of using java and a decent compiler compiler : see attached BNF generated for us by javacc.
I would maintain that using components across architectures is easier without the overhead of JNI (it is a bit of a pain to program) - and to simply implement in plain java. This way, the creator of the component doesn't have to worry about which architecture they need to target their code to - it just works.
What happens if I want to run the code on an SGI system ? Or MacOS X, or (etc. etc.) will the c++ source code for the filters always be available and guaranteed to port from system to system ? How many translators have compilers installed ? :-)
Of couse, you may still want to use COM, in which case, a single JNI wrapper for the java classes would be the right approach, but in general, JNI accesses should be as few as possible.
You may have gathered, this is a somewhat pro-Java stance, but I make no apologies for where my loyalties lie - I truely believe this is the way things should be.
cheers,
tim
> > > >On Fri, 2002-01-18 at 13:09, Yves Savourel wrote: > > > >>>Most interesting Yves - I've read through the Okapi docs and it sounds > >>>like a great project. Have you given any thought towards a Java-based > >>>version ? > >>> > John > > > > > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ > >