Today I posted a question to the the multitude of .NET Developers within my company.
"Is it worth while to use COBOL for .NET to help transition legacy programmers from the mainframe to .NET?"
The answer I got was a resounding "No!"
The three major points they raised follow:
- Although familiarity with the language syntax would help at first, they would soon fall back into writing procedural code which would end up being detrimental in the long run.
- The shock of learning a new language syntax will help in learning the Object-Oriented and Event Driven concepts required to write good code under .NET.
- The COBOL Language syntax does not lend itself to the concept of writing components and services.
What's your input?