One of the VAX computers I rescued from disposal at the height of the Y2K impending apocolypse came with licenses (PAKs for those in the know) for DEC COBOL, DEC RDBMS, and DEC FORMS. These three applications formed the backbone of payroll processing for the company that was tossing the VAX. This machine, processed the payroll for a bit over 5,000 employees on a "clustered" machine that had a combined total of 512MB…
> I can assure you that "Quickbook Payroll" would not be able to handle this on a similarly resourced x86 machine. Not even close.
Why? I've been into x86 databases since the Windows NT days and 5000 doesn't seem an impressive number to me.
I too have seen lots of badly written .NET code out in the wild. However, as with most languages, that is more a measure of the quality of the developer, than the quality of the language. As a C++ developer now writing C# using .NET that new language and framework are a pleasure to work with.
> However, as with most languages, that is more a measure of the quality of the developer, than the quality of the language. No, it’s more a measure of the quality of the development organization and process . The quality of individual developers is a factor here, but not the only one and often not the limiting one on software quality (and particularly often not on, e g., whether or not business requirements and syst…
Quite right — and to the extent that the blame goes to any individual developers, that comes back to the organization: do they pay well, offer a good working environment, etc.? One bad hire, sure, it happens but if it’s repeating that’s structural.
I'm just imagining the level of jaw dropping and brain exploding that would have gone on had that same headline been published in 1998. Obviously at this point almost three decades into the internet era no one really cares. We all know that "somewhere" old COBOL code is running, but in practice the companies managing the bulk of data for society didn't even exist before Y2K. Everyone with unmaintainable COBOL has lon…
The lack of comments vs position on front page is intriguing.
There's nobody here (besides maybe me) old enough to have anything to say.
I worked with COBOL just in time to fix Y2K problems, and I still have nightmares about it -- not about Y2K, mind you, but about COBOL and banking systems. Such a horrible, horrible programming language.
One of the VAX computers I rescued from disposal at the height of the Y2K impending apocolypse came with licenses (PAKs for those in the know) for DEC COBOL, DEC RDBMS, and DEC FORMS. These three applications formed the backbone of payroll processing for the company that was tossing the VAX. This machine, processed the payroll for a bit over 5,000 employees on a "clustered" machine that had a combined total of 512MB…
What's so burdensome about payroll processing? It seems straightforward enough.
One of the VAX computers I rescued from disposal at the height of the Y2K impending apocolypse came with licenses (PAKs for those in the know) for DEC COBOL, DEC RDBMS, and DEC FORMS. These three applications formed the backbone of payroll processing for the company that was tossing the VAX. This machine, processed the payroll for a bit over 5,000 employees on a "clustered" machine that had a combined total of 512MB…
Can't you get all this stuff with a hobbiest license and a full media kit? Doesn't macro32 on alpha or itanium run old VAX binaries transparently? Why keep the antiques? Even SimH seems a better option (assuming the licenses work). http://www.openvmshobbyist.com/news.php
You could, except that they stopped the hobbiest program sadly.