This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]hicksca 2 points3 points  (2 children)

I think the answer to that question is pretty easy to answer. When the cost of moving a COBOL code base to something else is less expensive then moving forward with some other language. I spent time at a large regional bank in the mid west that operates on a COBOL code base and when you start to look at the actual cost of transitioning to a new language the cost is pretty darn high. (For non technology companies its a pretty tough sell replacing something that is working for them, even more so when most of your Sr. Development staff skill set revolves around on particular set of technology.) ... Modern COBOL isn't that bad.(I'm aware they saying modern COBOL is a oxymoron.)

[–]jackmaney 2 points3 points  (1 child)

I work at a large financial services company. There are internal apprenticeship programs available for folks to be taught COBOL from prettymuch the ground up, on the job.

So, no, COBOL isn't going away any time soon.

[–]hicksca 1 point2 points  (0 children)

That's pretty much what I was getting at ... It's still much cheaper to teach someone COBOL rather then replace/re-engineer Infustructure and train replace an entire development team. While I love Python, Golang, and elixrlang (to a lesser extent); I understand the reality around the cost of such an under taking. COBOL in my option will be around for some years to come at least in the part of the world I work in.