News for hackers. Stuff that matters.
Re:The Deathrow OpenVMS Cluster by gaius on Friday August 01, 2014 @03:11AM (#8118689)
I guarantee something you do today will require some COBOL to be run on your behalf.
Re:The Deathrow OpenVMS Cluster by shmerl on Friday August 01, 2014 @03:37AM (#8118736)
That'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.
Re:The Deathrow OpenVMS Cluster by Allegrippus on Friday August 01, 2014 @05:34AM (#8118967)
I'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?
Re:The Deathrow OpenVMS Cluster by shmerl on Friday August 01, 2014 @02:26PM (#8121984)
> 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.

Re:The Deathrow OpenVMS Cluster by kjs3 on Saturday August 02, 2014 @12:01AM (#8123959)
We 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?
Re:The Deathrow OpenVMS Cluster by shmerl on Saturday August 02, 2014 @09:53PM (#8126740)
The reasons for using COBOL in any new project weren't explained, so whatever was "established" is irrelevant to the discussion.
Re:The Deathrow OpenVMS Cluster by kjs3 on Friday August 01, 2014 @08:46AM (#8119496)
I 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.