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 : INPR - Inprise to Borland (BORL) -- Ignore unavailable to you. Want to Upgrade?

To: Steve Wood who wrote (499)	7/14/1998 10:50:00 PM
From: Kashish King	Read Replies (1) \| Respond to of 5102

COM is a massive canyon of complexity coupled with an ant hill of functionality. COM is like a some throw-away high-school computer science project gone awry and given a failing grade. You can reuse COM components like you can reuse Microsoft Word: you don't have to buy a new copy of Word every time you run it. Not even the most experience COM developer can create a clean C++ application using COM. It is the ugliest, most archaic and bush league software infrastructure known to man, bar none. Derivation is a nightmare, aggregation is an abortion, remote access is an aborted nightmare. Java and Java Beans are clean, powerful, elegant, sensible, well though out and down right beautiful. As every programmer should know: premature optimization is the root of all evil. The Java environment is being aggressively optimized now that the infrastructure is pretty much stable. I suspect we will see exponential growth in the availability of vertical market Java Beans once it has been accepted by IT managers as THE standard. BTW, had they wanted to, Microsoft could have developed a vastly superior C++ framework but that would have competed with Visual Basic and they couldn't have that.

To: Steve Wood who wrote (499)	7/15/1998 8:33:00 AM
From: i-node	Read Replies (3) \| Respond to of 5102

I don't want to bore the thread by digging out some of Rod's 1-year-old (maybe more) discussions on the BORL thread of Java and how it would, within months, be the death of other languages; how it was a "done deal" that Java would be THE language of the future; how revolutionary this language with runtime (sorry, did I say runtime, I must have meant "virtual machine" was). This stuff just doesn't change that quickly. At the time, as today, Java'a acceptance is marginal, substantial Java-based apps are still eerily missing from store shelves, and the hype has died down considerably. People need to avoid jumping on the bandwagon at the first turn. I don't have a problem with Borland offering a Java product, but it is [still] WAY too early for a company's overall strategy to rely too heavily on it. IT MAY NOT MAKE IT (I know, we have all been told, a year or more ago, that it is a "done deal". But that doesn't make it so. Ultimately, it matters only whether the language is accepted in the marketplace, which still isn't happening).