Re: Saving CoBOL

"Howard Brazee" <howard@[EMAIL PROTECTED]
> wrote in message 
news:copj14ltndjh64t1rupc8tv4q9bk4hqsbb@[EMAIL PROTECTED]
>
> http://blogs.computerworld.com/saving_cobol
>
I enjoyed the responses more than the article itself.

No matter how you cut it, there is a huge current investment in COBOL and
it 
seems irresponsible to simply throw it away.

I think refactoring may be an answer. It has certainly worked for my own 
stuff. I'm still running COBOL components as unmanaged code in .NET and
have 
had no need to replace them so far.

The lack of jobs is going to be the main nail in the coffin.

The old-timers are fading away and the new guys can do the same stuff 
smarter and quicker with modern approaches and languages.

That's still noreason to throw away stuff that isn't broken...

Pete.
-- 
"I used to write COBOL...now I can do anything."