Hi James;
I think what a lot of other people are saying is that the API should
be written with *no* language in mind. Saying that Java "can be used to
drive the design of an API" bothers people because when Java "drives"
the design of the API you begin to create an API Java can work well
with without much regard to other languages. Other languages are left
to fend for themselves. It might even turn out that not all languages
can be use to drive the API, this is okay as well.
People want an API that works well - I am 100% sure we *all* want to
see this. If however, it turns out that it is easier to provide a
backend to this API using LISP, so be it, the Java folks have to work
a little bit harder if they want to use a Java backend. Of course,
the opposite of this holds true.
Java is really exciting, but so is LISP, TCL, Smalltalk, Objective C,
FORTH, Visual Basic, etc etc.
PS: this is *not* a flame, in the mail this is a response to James is only
trying to clear up some miscommunication from a difserent email message.
------------------------------------------------------------------------------
Neophytos Iacovou Distributed Computing Services
University of Minnesota 100 Union St. SE
email: iacovou@boombox.micro.umn.edu Minneapolis, MN 55455 USA