3 ms·
> for COBOL, or thought to produce an emulator facade that keeps the business logic of legacy code, but ports it to another platform, architecture, infrastruct
by raverbashing 8y ago
> for COBOL, or thought to produce an emulator facade that keeps the business logic of legacy code, but ports it to another platform, architecture, infrastructure
There are some, but the answer is: because COBOL is opinionated.
In terms of verbosity it makes Java look like a Haiku, and it's a weird mix of lower level and higher level constructs.
Classes? What are those? Code reuse?
It also talks (in weird ways) to things like green screen interfaces and saves data in "records" or builds "reports" (just try to create XML natively in Cobol)