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.

Strategies & Market Trends : ahhaha's ahs -- Ignore unavailable to you. Want to Upgrade?

To: GraceZ who wrote (5524)	10/22/2002 11:44:07 PM
From: ahhaha	Read Replies (1) \| Respond to of 24758

NetCOBOL is a COBOL development environment and suite of tools to build fast, mission-critical business systems on open platforms, including Microsoft's .NET Framework Fujitsu's COBOL isn't unique. The added value idea behind dotNET is common language runtime, for who would think that anyone's COBOL would run in an ASP? The HTML usually there could call a COBOL routine, but it would have to be compiled on the fly to run resulting in a hit on performance. From O'Reilly: However, several of the goals of the .NET platform are fairly lofty and not at all guaranteed to fly, at least not in the short term. The IL common language runtime, for example, has some fairly significant hurdles to overcome before it has any real payoff for developers. Each language that wants to integrate with the component runtime has to define a subset/superset of the language that maps cleanly into and out of the IL runtime, and has to define constructs that provide the component metadata that IL requires. Then compilers (x-to-IL and IL-to-x) will have to be developed to both compile language structures (objects, components, etc.) into IL component bytecodes, and also generate language-specific interfaces to existing IL components. Nonetheless, due to WIN's ubiquity this is being done on a practical basis.