Jim Lavin

Its all 'bout re-use

  Home  |   Contact  |   Syndication    |   Login
  18 Posts | 0 Stories | 7 Comments | 0 Trackbacks

News

Twitter












Tag Cloud


Archives

Post Categories

My Other Blogs

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:

  1. 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.
  2. 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.
  3. The COBOL Language syntax does not lend itself to the concept of writing components and services.

What's your input?

posted on Wednesday, August 22, 2007 3:08 PM

Feedback

# re: Legacy Stepping Stones to .NET Development 9/19/2007 1:51 PM Aaron Kowall
I support the rest of the developers in your company :) In my experience, syntax is the least of the worries. The semantic change and learning the frameworks and OO/EventDriven/Service Orientation are WAY harder than the syntax change. Moving to C# (or even VB.Net) causes a clean break which is quite frankly easier on the brain.

Post A Comment
Title:
Name:
Email:
Website:
Comment:
Verification: