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: David R who wrote (9691)	4/1/1998 2:33:00 PM
From: Kashish King	Read Replies (1) \| Respond to of 10836

Component based SW with C++ works great on paper, but implementation is too dependent on programmer. And COM is not dependent on the programmer? What drivel. Inproc Com gives nice encapsulation of reusable objects. Reuse of objects is nothing new, we were doing that level of reuse with assembly language. What COM is missing is inheritance because the designers were working in a clueless vacuum. It forces our team to keep their interfaces clean. What does COM have to do with keeping an interface clean over Beans, CORBA or even C++. More meaningless drivel right out of your MSDN subscription. I understand this technology, David, and you aren't making any sense. Exposing our objects to a scripting environment requires COM. As compared to what? Java Beans and applets were designed for use with scripting languages. So the notion that you need COM for that only applies to C++ interfaces. Moreover, COM is an interface mechanism only, unlike homogeneous Java technologies.