For the record, this is what *I* see as the strongest possibility,
although I'm keeping an open mind at this point. A reasonably
straightforward object-oriented language, which could be automatically
generated by some other system if desired, has some strong advantages
and no disadvantages that I've seen yet.
I don't have as strong an opinion about *which* language got used.
I've been reading into Java, and that's quite pretty; if (as the
stories I've heard say) Sun is planning on releasing the Java tools
into the public domain, then it's certainly a strong contender. On
the other hand, we could probably do just fine with something Lispish,
a la Geomview...
(Of course, if we went with Java, that opens things up in some new and
interesting ways. I suspect that, for example, Ada 95 could generate
fairly nice Java Machine output, and give you a little extra oomph on
the programming end.)
> If what I am
> proposing above is what is being discussed as an API, I think that we
> should clear the air, because that is not an API.
Wellll, sorta. I mean, API means "Application Program Interface". If
we are specifically choosing a language and building our tools such
that application programs can use that language to interact with the
browsers, then that *is* an API in the most literal sense. Just not a
traditional one...
-- Justin
Who doesn't see this as a strict
"API vs Language" issue...
Random Quote du Jour:
"If where you go ain't there you are
It must be here, talk.bizarre."
-- Blair