• To: <xml-dev@l...>
• Subject: Re: XML moves COBOL into the .NET and J2EE arenas
• From: "Ken North" <kennorth@s...>
• Date: Fri, 14 May 2004 13:41:02 -0700
• References: <000501c4396d$1c38f5d0$0200a8c0@barry>

<< there is more than a sizable investment in COBOL prior to recent years.

My point was not that the investment in COBOL is a recent phenomenon, but that
it's continuing -- COBOL didn't die in the 80s. There are about 2 million COBOL
programmers versus 3 million Java and 300,000 Perl.

The reason why we still have 200 billion lines of COBOL running today is
standardization and portability. Before the UCSD p-system,  ANSI C, and the Java
VM, COBOL was a favored solution for writing code for multiple platforms.

<< watching where COBOL goes is actually a proxy for listening to the customer.

It's also an indicator that organizations will commit (long term) to
vendor-neutral technologies based on standards.

• Follow-Ups:
  • RE: XML moves COBOL into the .NET and J2EE arenas
    • From: "Paul Sumner Downey" <Paul.Downey@w...>
  • RE: XML moves COBOL into the .NET and J2EE arenas
    • From: "BarryTauber" <btauber@i...>
  • Re: XML moves COBOL into the .NET and J2EE arenas
    • From: Tim Bray <tbray@t...>

• References:
  • RE: XML moves COBOL into the .NET and J2EE arenas
    • From: "BarryTauber" <btauber@i...>

• Prev by Date: Re: java environment variables when setting up sax
• Next by Date: XDR: External Data Representation
• Previous by thread: RE: XML moves COBOL into the .NET and J2EE arenas
• Next by thread: Re: XML moves COBOL into the .NET and J2EE arenas
• Index(es):
  • Date
  • Thread