COBOL case is bit different. You can’t just modernize millions of lines of code that is functionally unique without service disruption - and services that uses COBOL that large often tends to be very sensitive.
The fact that COBOL as a language is both atrocity to either use or read didn’t help that either.
SamirCasino@lemm.ee 1 year ago
Been in the industry for 10 years and i deeply disagree with you. I work in COBOL.
Not that migrations don’t happen, but in my experience, many, many companies kick that can down the road each year, because migrating huge and critical services is extremely costly, time-consuming and risky. In the short term, just paying people to maintain the dinosaurs is waaaay cheaper.
Also, it’s extremely easy to get a job in it ( my company now hires people with no IT background and tries to teach them cobol from scratch ), because even though it’s a niche, the demand for it still outweighs the supply of people willing to learn it.
Will it die out eventually? Maybe. I’ve been hearing about its death for a decade, so i’ve become skeptical about it in the short-term.
oxideseven@lemmy.ca 1 year ago
I’ll learn cobol. What company? I do have an it background as a bonus though.
SamirCasino@lemm.ee 1 year ago
Good luck to you!
I’d rather not dox myself, but i can tell you i’m in eastern europe working for a western european bank. COBOL is still heavily used in the banking and insurance sectors, by companies that started using it 50 years ago.
If you do manage to learn the ropes, the salary does tend to be above average for a mid-level programmer.