Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : All About Sun Microsystems -- Ignore unavailable to you. Want to Upgrade?

To: uu who wrote (8107)	3/8/1998 5:36:00 AM
From: Kal	Respond to of 64865

but if j++ 6 id jdk 1.1 compatible, why would a developer use any microsoft-specific methods or classes etc? If it does soppurt 1.1, I probably would end up using it. I used visual cafe and j++, I liked j++'s interface more. But I'd still be suspicious of hidden features in their new j++.

To: uu who wrote (8107)	3/8/1998 11:13:00 AM
From: Kashish King	Respond to of 64865

J++ does have a very unique development environment and user interface that comes very natural to the users and very easy to learn and work with. This is partially due to the fact that most Java Developers (if not all) have been working with C++ and most have come to use no other C++ development tool but Microsoft's Visual C++ product. Addi, Microsoft's development efforts have and will continue to be geared toward Visual Basic at the expense of C++. That's why their form generator has changed little in the last 8 to 10 years and it won't likely be upgraded in the future -- it's called the dialog editor. The whole system is macro-based and it's really only those who don't understand the Windows event model and/or C++ that benefit in any significant manner from their so-called interactive development features. It can't be extended to support non-Microsoft classes. J++ is nothing more than the same, extremely lame (please note: extremely lame) C++ development environment. Perhaps you're not familiar with truly interactive, two-way tools? Under no circumstances would we consider using J++ and not simply because it's the same outdated development environment as C++. If you're wondering why it's so lame, it's because Microsoft wants it that way; they want Visual Basic to be the tool of choice and they want ActiveX to be the component model of choice. Now that they see the momentum behind Java building even more rapidly they are forced to respond. Microsoft is scared to death that developers will create software for a standards-based, cross-platform tool and in addition to bashing it they will attempt to co-opt or subvert it. Microsoft's J++ is a slightly updated version of their C++ development environment with a few Java tools and wizards added. It contains no support for Rapid Application Development, no support of two-way tools, no support for visual layout using Java's variety of layout managers, no cross-platform support, and no Java Component Library.