3 ms·
> The cluster supports many programming languages, including: BASIC, C/C++, Fortran, Cobol, Ada (on Alpha), Bliss, Macro32, DCL scripting, Java, and Pascal. Th
by shmerl 12y ago
> The cluster supports many programming languages, including: BASIC, C/C++, Fortran, Cobol, Ada (on Alpha), Bliss, Macro32, DCL scripting, Java, and Pascal.
That's probably historical, but I wonder what's the point to advertise that the cluster supports Cobol for example?
- jmspring 12y agoSome people might be looking for a machine to play around with Cobol?
- iancarroll 12y agoIf your project supports x why wouldn't you tell people?
- gaius 12y agoI guarantee something you do today will require some COBOL to be run on your behalf.
- shmerl 12y agoThat's very possible, but I doubt anyone would make something new using it. As far as I know, it's used only in cases when switching is too difficult.
- Allegrippus 12y agoI'm aware of several prominent companies in the Pittsburgh region that were on centralized mainframes and now use Micro Focus or some other "modern" COBOL for their core systems. These aren't legacy but are actively developed and extended. To look at the screens, etc., you'd likely never guess that the underlying code is COBOL. If it does the job and serves the business well, why switch?
- shmerl 12y ago> If it does the job and serves the business well, why switch? That's of course understandable (for keeping legacy systems), but new systems deployed with using Cobol is not so expected.
- kjs3 12y agoWe established that your limited experience in the business hasn't exposed you to a lot of what is going on outside of what is reported in HN. Why do you insist in on flaunting that fact?
- shmerl 12y agoThe reasons for using COBOL in any new project weren't explained, so whatever was "established" is irrelevant to the discussion.
- kjs3 12y agoI was at a Very Large insurance company last month where they discussed a suite of new Cobol applications they were deploying and what infrastructure they were going to need to deploy them (very large $$$ worth, btw). They could have done it in Java (and do many things in it), but believed that because of their experience and the critical nature of the apps, Cobol was much less risky. As a tangent, they tried at one point to change their development language to Smalltalk (because at the time it was what the cool kids wanted to use), but we don't mention that in their presence. Once your experience in development evolves beyond buzzword-bingo web apps and obsession with faddish language features, you find all sorts of real work being done in uncool things like Cobol, Ada, Fortran, VB, etc.
- dlitz 12y agoBecause COBOL is alive and well. It's not interesting, but it's far from dead. A friend of mine works on a COBOL system that's responsible for calculating pension payments for former government employees. COBOL is good enough for this application, since it's basically just a glorified pile of if-statements. Rewriting everything in the hot-new-language-of-the-year would almost certainly introduce bugs, so instead of screwing up people's pension checks every couple of years, they just pay a my friend to know COBOL and to keep the rules up to date. There's still enough of a community behind COBOL that there's really no reason not to do this. COBOL compilers continue to be maintained, and even the language itself is getting updated (see e.g. https://en.wikipedia.org/wiki/COBOL#COBOL_2014 https://en.wikipedia.org/wiki/COBOL#COBOL_2014).
- shmerl 12y ago> Rewriting everything in the hot-new-language-of-the-year would almost certainly introduce bugs Yes, that's the point I usually hear. I.e. that it's used for legacy applications, just because switching to anything else doesn't worth the effort. I'd be more surprised however when it would be used for any new project.