To: Philip Copeland who wrote (1141 ) 9/8/1998 1:55:00 AM From: Kashish King Read Replies (2) | Respond to of 5102
I think it's safe to say that you're not actually using the product personally. I'm sure you have several people rolling on the floor laughing their butts off with your praise -- ROFLBOWYP. As for the ancient Peter Coffee reference, he writes magazine articles. If we shift from object-oriented to an n-space paradigm tomorrow he'll be a self-proclaimed expert by Wednesday. He is utterly clueless. In terms of evaluating tools, the Siskel & Ebert approach doesn't cut it. JBuilder maybe adequately designed (I would give it a D, tops) but your claim that it's reliable is completely at odds with the experience of most of the INPR longs on this thread who have used it, never mind the newsgroups. Inprise's solution is to ask everybody to get NT and add more memory. As is often the case, users already have 256 Megabytes and they're already running NT. Inprise's then suggests that you do their job for them: test it, detail the problem and submit a bug report as if our customers, or employers, have the time and money to debug Inprise's products for them. Look, this isn't open for debate: The product is unfit for release. What some of the more honest support people will tell you is that it's unstable under Windows 95 -- that's clearly one of the several deflection angles, it's equally bad under 95 and NT. Others will tell you it's Sun's JVM. Needless to say, users don't care whose fault it is. Java Beans Express takes the cake in terms of instability. I wonder if the team came back from vacation to find Del shipped the product, it's really that bad. By the time Del and his crew learn how to direct software development managers it will be too late. I agree with the previous caller: if you see Del Yocam at the helm, short it and ask questions later.