Article View: borland.public.jbuilder.java.language
Article #16725Re: JBuilder to stay?
From: Vasudevan Srinivasan
Date: Mon, 25 Jan 1999 00:00
Date: Mon, 25 Jan 1999 00:00
22 lines
1581 bytes
1581 bytes
Hi I did feel a bit disappointed on OWL not "keeping" up with MFC, given that OWL had a good start. (it was ludicruous to compare OWL2 and VC1.5 at one point of time). I have used both and my non-biased opinion would be that OWL was much more intuitive and easier to use. IMO, the MFC has now become too complicated. (If you dont believe me, just get some recent MSJ issues and you will find that the simplest questions have complicated answers.) Anyway, the java language and the ides were here not long ago, and I believe it will hang around for some more time. And if the situation changes, the simplest thing to do for all the developers is to follow it. you may like it or not, application developers are always at the mercy of tool developers who are at the mercy of os developers who are at the mercy of hw engineers who have their own laws ;-) Vasu Steve Guo wrote: > After Borland discontinued OWL, I hesitate to use any Borland/Inprise > product including JBuilder? I am wondering how you guys feel? > Thanks
Technical Details
Message-ID:
<36ACB575.C518CE34@netrisk.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<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: Vasudevan Srinivasan <vasudevan@netrisk.com> Subject: Re: JBuilder to stay? Date: 1999/01/25 Message-ID: <36ACB575.C518CE34@netrisk.com> X-Deja-AN: 436768869 Content-Transfer-Encoding: 7bit References: <36A95DCD.89076CCA@sprintmail.com> Content-Type: text/plain; charset=us-ascii Organization: Another Netscape Collabra Server User Mime-Version: 1.0 Newsgroups: borland.public.jbuilder.java.language