TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

20 Years in the Making, GnuCOBOL Is Ready for Industry

180 点作者 cglong大约 1 年前

16 条评论

NikolaNovak大约 1 年前
&gt;&gt;Get those punch cards back out!<p>I get that&#x27;s (probably!) a joke, but it misrepresents COBOL as something <i>completely</i> stuck in the 70s. And, y&#x27;know, it isn&#x27;t exactly the fanciest language in the world, but we still have several programmers on our project and they&#x27;re spitting out new code every day of their life, no punchcards:).<p>(And it&#x27;s not on a mainframe either - it&#x27;s running primarily on AIX, with some of Windows and Linux).
评论 #39729941 未加载
评论 #39729988 未加载
评论 #39729830 未加载
评论 #39730453 未加载
评论 #39731549 未加载
评论 #39732136 未加载
评论 #39734127 未加载
Borborygymus大约 1 年前
In the late 90s I worked for a vendor of CRM software. A fair bit of billing and payment-handling code was written in COBOL. Wasn&#x27;t mainframe - ran on a couple of flavours of proprietary Unix. The COBOL compiler vendor was Microfocus.<p>I didn&#x27;t have any training in COBOL, but found it pretty easy to read and understand - at least for the fairly simple business logic in a billing system. I didn#t have to write anything - just do some debugging when it didn&#x27;t output as expected. Wouldn&#x27;t want to do anything too mathsy or heavy string processing with it, but it seemed a good fit for the application.<p>I did some more work for the same company later. A descendent of that software is still running today. At some point between 2000 and the late 20-teens they migrated to Linux, and I think at that point used some sort of COBOL-to-C transliteration software, and the Microfocus compiler was jettisoned. Not sure if the decision was because Microfocus was very expensive (I have heard that, but have no personal experience of it), or just didn&#x27;t support Linux at that time.<p>That transliterated code is still running today, but a bit of a nightmare to maintain. If GNU Cobol has been mature enough whenever that migration happened, I suspect it would have been a much better approach than transliteration. Too late for that code base though.
评论 #39730896 未加载
fredsmith219大约 1 年前
The vast majority of COBOL in production runs on IBM mainframes in conjunction with JCL (Job Control Language). If you are looking to offload COBOL from a mainframe to a cheaper platform JCL is a must. I love that this project exists but it’s only one half of a solution to migration off of a mainframe.
评论 #39730075 未加载
评论 #39733441 未加载
评论 #39729737 未加载
seanhunter大约 1 年前
But you need a modern enterprise-quality framework. Can it run Cobol on Cogs?<p><a href="http:&#x2F;&#x2F;www.coboloncogs.org&#x2F;INDEX.HTM" rel="nofollow">http:&#x2F;&#x2F;www.coboloncogs.org&#x2F;INDEX.HTM</a>
Zenst大约 1 年前
&quot;Compliance-wise, it passed 97% of COBOL 85 conformance tests, a success rate not yet achieved by proprietary vendors, Sobisch boasted.&quot;<p>Thinking about that if you step back is amazing, to think a standard written in 1985 (I was doing COBOL back then into the 90s) has yet, even today not had any of the big names&#x2F;players meet full compliance nearly 40 years later.<p>I&#x27;d love to read more about that aspect
评论 #39734143 未加载
评论 #39732098 未加载
评论 #39731650 未加载
musicale大约 1 年前
COBOL&#x27;s boilerplate doesn&#x27;t seem that much worse than what Java programmers lived with for decades.
评论 #39730867 未加载
评论 #39731720 未加载
michaelsbradley大约 1 年前
Don’t miss the <i>GnuCOBOL FAQ and How To</i>, perhaps one of the largest such documents ever compiled:<p><a href="https:&#x2F;&#x2F;gnucobol.sourceforge.io&#x2F;faq&#x2F;index.html" rel="nofollow">https:&#x2F;&#x2F;gnucobol.sourceforge.io&#x2F;faq&#x2F;index.html</a><p>(may cause mobile browsers to crash while loading)
rhaps0dy大约 1 年前
&gt; the past three years, it has received attention from 13 contributors with 460 commits.<p>That doesn’t sound like very many commits. Pretty mature!
nxobject大约 1 年前
&gt; There’s no support yet for objects or messages in GnuCOBOL. &gt; Objects was “a nice feature from COBOL 22, which isn’t used that much,” Sobisch said. &gt; Messaging just got reimplemented recently, and is still a new feature for the COBOL crowd to grapple with, Sobisch said. So, no support in GnuCOBOL yet.<p>COBOL 2022. My god.
zulban大约 1 年前
That hello world program is brutal. Truly, the language is the first of its kind.<p>Hopefully this helps fleets of developers bring their legacy code (more legacy than most of us can imagine) into a modern stack, and start applying modern SWE principles to it.
评论 #39732122 未加载
ddgflorida大约 1 年前
Well that&#x27;s exciting :)
mise_en_place大约 1 年前
It’s interesting but will anyone actually use it? z&#x2F;OS for example doesn’t have a hierarchical file system. The version of COBOL they bundle supports data sets I’d imagine. Legacy folks will be hesitant to switch to it as well. When I worked at a bank they couldn’t even use the latest Java, due to compliance and regulatory reasons.
globalnode大约 1 年前
one of my subjects at uni in the 90&#x27;s (IT degree) required me to learn cobol. god i hated that class. thankfully i dont remember much of it. it was actually before we learn&#x27;t c&#x2F;c++, also VB was a big thing then too.
proneb1rd大约 1 年前
Very exotic. Does it support multi threading? What kind of things can be done with it?
评论 #39729808 未加载
xunil2ycom大约 1 年前
I award them no points, and may God have mercy on their souls.
评论 #39731468 未加载
mseepgood大约 1 年前
What took so long?
评论 #39733329 未加载