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: dybdahl who wrote (10824)	12/20/2003 8:46:08 AM
From: i-node	Read Replies (1) \| Respond to of 10836

Can you explain what you mean by the BCB/CBuilderX situation? Basically, they discontinued BCB, replacing it with CBX, and gave us [BCB users] no migration path WHATSOEVER. CBX does not support VCL, which is, of course, the basis for all the BCB projects out there. Where Delphi users are going to have a reasonable transition to .net, BCB users are essentially left with no way out other than total rewrites. Had they devoted SOME resources to providing VCL support in CBX, they could have had a ready market for the product. As it is, they have produced what amounts to a beta of CBX that few, if any, BCB users are going to move to. There weren't that many of us, but just discarding the user base as they have done seems utterly stupid. I believe we're moving to VS as well. We've just finished a 3 year development project in BCB and feel that Borland is really dropping the ball and there is no way we're sticking with BORL after this. We could pretty easily move to Delphi, but then we'd just be doing it again a year or two down the road. I think Microsoft has won the war. There is no compelling reason to use Borland tools at this point, and there are tons of reasons not to.