[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: XML moves COBOL into the .NET and J2EE arenas

• To: "Ken North" <kennorth@s...>,<xml-dev@l...>
• Subject: RE: XML moves COBOL into the .NET and J2EE arenas
• From: "Paul Sumner Downey" <Paul.Downey@w...>
• Date: Sat, 15 May 2004 07:28:08 +0100
• Importance: Normal
• In-reply-to: <000601c439f3$ca7de160$1601a8c0@DURANTE>

Ken

this is interesting stuff and matches my own experience working in a very
large company. What irks me most is a high and mighty attitude from the
Java/.NET/Siebel/SAP/etc brigade towards 'card-wallopers'. The mainframe
guys i know tend to be very good and have a experience of building very
large scale critical systems often way beyond the experience of the vast
majority of today's commercial programmers.

As hard as companies try to move data onto 'packages' they still find COBOL
running the business. I've spent the last 5 or so years helping to migrate
COBOL interfaces into XML, SOAP and then WSDL precisely because of this.
What has enabled this to happen is the programming skills of my mainframe
colleagues who wrote an efficient SOAP/XML module in COBOL for an existing
in-house middleware framework - something thought by many to be simply
not possible!

I note from your figures that Java is the new COBOL, which makes me happy
to remain a Perl & Python hacker :-)

Paul


-----Original Message-----
From: Ken North [mailto:kennorth@s...]
Sent: 14 May 2004 21:41
To: xml-dev@l...
Subject: Re:  XML moves COBOL into the .NET and J2EE arenas


<< 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.








-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.php>

• References:
  • Re: XML moves COBOL into the .NET and J2EE arenas
    • From: "Ken North" <kennorth@s...>

• Prev by Date: Re: XML moves COBOL into the .NET and J2EE arenas
• Next by Date: RE: XML moves COBOL into the .NET and J2EE arenas
• Previous by thread: RE: XML moves COBOL into the .NET and J2EE arenas
• Next by thread: RE: ISO and the Standards Golden Hammer (was Re:[xml-d ev] You call that a standard?)
• Index(es):
  • Date
  • Thread