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 : BORL: Time to BUY! -- Ignore unavailable to you. Want to Upgrade?

To: Scott McPeely who wrote (9635)	3/30/1998 12:42:00 AM
From: Kashish King	Read Replies (1) \| Respond to of 10836

What were C's (remember BCPL) design goals and look where that went? The Java language, Java Beans and Enterprise Java Beans simply can't be compared to the historical anathema which DCOM and COM represent. Clearly nobody can fault Microsoft for not coming out and admitting that COM and DCOM should not have been developed in a vacuum by some rather untalented and myopic DOS hacks who apparently had never been outside, nevermind solicited outside opinions. That is why Microsoft is now under siege by Java. It's not so much the language or the promise of WORA, it's the component model, the elegance of inheritance and the benefits of Java's combination compilation/interpretation model. Microsoft hasn't ever delivered a successful technological basis, they have only co-opted the proven technology of others. They never introduced anything of their own, never, ever, not one time. As far as XML is concerned, it's just a document format. XML is new and improved SGML developed to address the serious shortcomings of HTML. What does XML spell? It spells the end of the road for Microsoft Word's dominance as smaller, faster, cheaper, more productive and more reliable wordprocessing software (written in Java) from a variety of companies will offer total interoperabilitynessment between documents. Java and XML were made for each other. Getting back to DCOM, that abortion doesn't have a snowball's chance of succeeding over EJB and EJB doesn't even exist yet. EJB is just a specification. Does that give you some idea of just how bad DCOM really is to be beaten by somebody yelling BOO!? Make no mistake about it, it is that bad. I'm starting to feel sympathy for Microsoft having come all this way only to found asleep at the switch; then I remember how the company used the extent to which an approach was proprietary as the primary criterion for deciding on a direction.