Re: JBuilder to stay?

Article View: borland.public.jbuilder.java.language

Article #16710

Back to borland.public.jbuilder.java.language Previous Next

#16710

From: Doug Chamberlin
Date: Sun, 24 Jan 1999 00:00

19 lines
1459 bytes

On Fri, 22 Jan 1999 21:27:41 -0800, Steve Guo <sguo@sprintmail.com>
wrote:

>After Borland discontinued OWL, I hesitate to use any Borland/Inprise
>product including JBuilder? I am wondering how you guys feel?
>Thanks

If you are looking for longevity in class libraries, you will have to
build your own. Even then, it may not last as long as you wish. That's
just the state of the industry and is not a Borland/Inprise specific
issue.

Regarding JBuilder, Inprise has been working closely with Sun to
define and implement JavaBeans and some of the other API collections.
it is really up to Sun to declare the longevity of these, not Inprise.
JBuilder will have to support whatever common API set emerges in the
Java world. At least in the Java world they have instituted the
"deprecation" tag so that you will know ahead of time when something
is going to disappear.

Technical Details

Message-ID: <36ac2ce8.224290931@forums.inprise.com>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

References: <36A95DCD.89076CCA@sprintmail.com>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f74b3,b9cedcebc684c61
X-Google-Attributes: gidf74b3,public
From: dchamberlinNOSPAM@dlawton.com (Doug Chamberlin)
Subject: Re: JBuilder to stay?
Date: 1999/01/24
Message-ID: <36ac2ce8.224290931@forums.inprise.com>
X-Deja-AN: 436314419
Content-Transfer-Encoding: 7bit
References: <36A95DCD.89076CCA@sprintmail.com>
Content-Type: text/plain; charset=us-ascii
Organization: D. Lawton Associates
Mime-Version: 1.0
Reply-To: dchamberlinNOSPAM@dlawton.com
Newsgroups: borland.public.jbuilder.java.language

Reply to Parent Message