So says the FCW, in this article.
What really surprised me was not the continuing use of COBOL in legacy applications, but the fact that a quarter of colleges still teach COBOL and for some it's still a required subject. I would have thought that COBOL was so old-fashioned and unappealing that it would have died out in the realms of academia, even though there's still a need for people who know it.
For legacy work, I suspect there's still things where it works pretty well. Consider the example of payrolls, one of the early applications of computers. You do payrolls every two weeks, or every month, which means batch processing must work okay. No need for fancier languages which support objects or whatever is today's hot concept.
I started programming in COBOL back when I was disillusioned with my bureaucratic career. Then, after I stayed in the bureaucracy, I got quite good with WordPerfect macros, back before the WYSIWYG days. Finally I did some Javascript in the mid 90's. But these days Python seems well beyond me, and not something useful. It's a shame; there was a rush of satisfaction every time you completed something and ran a test and it worked correctly. Of course, that rush was usually followed by the frustration of failure when the next test bombed.
Did anyone notice that Google had a tribute to Rear Admiral Grace Hopper, one of the mothers of COBOL?
No comments:
Post a Comment