2 ms·
Few people want to program in COBOL; but businesses still depend on running COBOL code. Reminds me of another language: JavaScript. The developers who didn't w
by derefr 9y ago
Few people want to program in COBOL; but businesses still depend on running COBOL code. Reminds me of another language: JavaScript.
The developers who didn't want to code in JavaScript, solved the problem of having to deploy JavaScript by creating other languages that compiled to JavaScript: CoffeeScript, TypeScript, Elm, ClojureScript, etc. And, more recently, by just turning the JavaScript interpreter into a glorified low-level VM, through WASM, so that it can be programmed in any language.
Why hasn't this approach been taken with COBOL?
With such a language in hand, you could take existing codebases (or compiled binaries) and write a decompiler that would convert them to your language of choice, so that the whole project could exist in the new form. Or, more simply, you could just write new modules (and rewrite any modules you have to change) in the new language, leave old modules as COBOL, and then link them together.