Not a lot of Cobol programmers much after that.
It's funny... my COBOL professor told us that COBOL was going away... yet here we are some 30 odd years later and it's still the mainframe language of choice.
Mainframes are a relic of the age before persoanl computers. Luckily for the few cobol programmers left out there, there are a few companies in industries where mainframes are still useful.
Your COBOL professor probably had not considered the government when he said COBOL was going away. And bankers.Like the DoD...
Your COBOL professor probably had not considered the government when he said COBOL was going away. And bankers.
That's kinda the way I felt at 00:01 on January 1st 2000. I was a Cobol programmer at the time.
Mainframes are a relic of the age before persoanl computers. Luckily for the few cobol programmers left out there, there are a few companies in industries where mainframes are still useful.
No one is building new data centers around mainframes. The businesses which use them and continue to update them, already have a significant investment in existing systems and don’t want to spend the money to replace them as long as it’s cheaper just to maintain them.Or just about any business that needs to crunch a huge amount of data in one swell foop (as opposed to real time). I think everyone thought client-server systems were going to take over that function, but so far, mainframes are still the best at what they were designed to do. They're lousy at other things.
I'm thinking if you were consulting, though, that it was the happy time. If employed by a large company using COBOL a lot, you were just overworked