On Wed, Dec 08, 1999 at 12:07:07AM -0500, Nelson Minar wrote:
> I think we can all work together on this. A lot of us in the Linux
> community are annoyed and mystified by Sun's years-long snubbing of
> Linux in the Java world. It honestly makes no sense. The press release
> that came out today did no good, either, ignoring the Blackdown
> contribution entirely. But I think we're all happy to see Inprise
> devote effort to a Java/Linux port. Thank you!
You're very welcome, yours is one of the few positive messages I got today
:)
> I think Inprise could help repair some bad feelings by making some
> official statement of thanks and respect to the Blackdown community.
> It never costs you to pay your props. A Slashdot story would be one
> good way to do this, or a letter to Linux Weekly News (publishes
> Thursdays), or even a note on your own release page.
Hopefully this has already been taken care of.
> It would be helpful if you made sure the Inprise team gets a summary
> of the discussions here.
Ok.
> I have to disagree with you on the rest of this, though:
>
> >The bottom line, and I didn't see a post about this, is that now
> >Linux has a fully functional JDK/JRE that can be used to port
> >thousands of applications.
>
> No, Inprise is the third Linux JDK/JRE that can run thousands of
> applications. Blackdown was there at the beginning, and IBM beat
> Inrpise to it too. Inprise is different in starting out with JDK 1.2.
> Smart move and useful, I think. But again, Blackdown was there first.
> You're even using their code.
Yes, I'm not denying this, my point was that today, because of both ports
and the combined effort of Blackdown and Sun/Inprise the Linux community has
a Java implementation that can compete with the ones of Solaris or Windows.
The current IBM port,1.1.x, is of no use for us because we need full JDK 1.2.2 support
Previous versions of the JDK were not mature enough to make it feasible for
us to write the entire JBuilder IDE in Java. Today's version is completely
native-code free and runs at the right speed. JBuilder stresses the JDK so
much that even the stock 1.2.2 is not enough, in fact our Solaris release
requires 1.2.2-004. It's not that we are picky, we just couldn't implements
some features without some code fixes. An example. JBuilder has Emacs
emulation, with the standard Swing of 1.2.2 if you press Alt-d or Ctrl-space
Swing will pass also the "d" or the blank in the editor. While the event is
processed correctly the extra character is unaccetable, at least for us.
Probably we are not the only ones that found this bug, hopefully other
developers will benefit from this fix.
> Well, no, the beginning was several years ago. And we've been hanging
> on tight, and advocating, and a few folks have worked their asses off
> building a codebase that wasn't even acknowledged in the press
> release. Can you understand why people are a bit annoyed?
I can understand it and I have been in the chorus with all the others
screaming and being ridiculized because of that. It's the story of my life,
some of us are just born wired to swim upstream :)
My comment was a hint of things to come...
--
Paolo Ciccone
JBuilder dev.team
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
