COBOL: Thinking about it wrong
1–10 of 116 posts
Re: COBOL: Thinking about it wrong
#2Re: COBOL: Thinking about it wrong
#3Re: COBOL: Thinking about it wrong
#4Re: COBOL: Thinking about it wrong
#5Re: COBOL: Thinking about it wrong
#6Re: COBOL: Thinking about it wrong
#7You know you're in trouble when "There's a syntax file for VSCode." is the height of your modernity.
Re: COBOL: Thinking about it wrong
#8COBOL is easy. JCL is the hard part.
Re: COBOL: Thinking about it wrong
#9People that have not been exposed to legacy industries (banking, insurance, etc) would simply not believe how many of these large/huge companies run the majority of their business on an IBM mainframe running COBOL code. I've seen it firsthand and I didn't believe it. For them, it just works.
Re: COBOL: Thinking about it wrong
#10I'm pretty sure I'm thinking about it right. How much COBOL code can run on a regular Ubuntu machine? What's the package manager for OSS packages? What test frameworks are in common use? You know you're in trouble when "There's a syntax file for VSCode." is the height of your modernity.
All of it. GNU Cobol exists, as do proprietary solutions from companies like Micro Focus that target the JVM and .NET (which is what you're looking for for a real COBOL solution).
But why is it so important to run COBOL on Ubuntu? If you need Linux, create a Linux LPAR on your mainframe.
> What's the package manager for OSS packages?
COBOL code runs Western civilization. Not having muh NPM is a feature, not a bug.
> You know you're in trouble when "There's a syntax file for VSCode." is the height of your modernity.
Dude. COBOL has entire modern IDEs written for it.