Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.os.vms    |    DEC's VAX* line of computers & VMS.    |    264,096 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 262,866 of 264,096    |
|    =?UTF-8?Q?Arne_Vajh=C3=B8j?= to bill    |
|    Re: Bootcamp    |
|    12 Jul 25 10:41:01    |
      From: arne@vajhoej.dk              On 7/12/2025 9:35 AM, bill wrote:       > On 7/11/2025 8:16 PM, Arne Vajhøj wrote:       >> The idea of a 1:1 port is usually bad. Yes - you can implement the       >> exact same flow of your Cobol application in Java/C++/Go/C#,       >> but that only solves a language problem not an architecture problem.       >       > The biggest problem with this the idea of going from a domain specific       > language to a general purpose language. While you can write an IS in       > pretty much any language (imagine rewriting the entire government       > payroll currently in COBOL in BASIC!!) there were real advantages to       > having domain specific languages. But then, no one today seems to even       > consider things like efficiency. Just throw more hardware at the       > problem.              That argument made sense 40 years ago, but I don't think there       is much point today - the modern languages have the features       the need like easy database access and decimal data type and       the missing features like terminal screen and reporting are no       longer needed.              >> You need to re-architect the solution: from ISAM to RDBMS,       >       > This is the only one I totally agree with but the original problem       > had nothing to do with the language. It had to do with the fact that       > RDBMS wasn't around when COBOL was written. I have been doing COBOL       > and RDBMS since 1980 and it was old code when I got there.              True.              But it is still a relevant example of where 1:1 will go wrong. If       you have a Cobol system using ISAM files, then do not want to convert       it to a Java/C++/Go/C# system using ISAM files.              >> from vertical app scaling to horizontal app scaling,       >       > Not really sure what this means. :-)              You can call it cluster support.              If you run out of CPU power, then instead of upgrading from a       big expensive box to a very big very expensive box then you just       add a cluster node more.              >>                                      Â                      from 5x16 to       >> 7x24 operations etc..       >       > Certainly don't get this. Every place I ever saw COBOL was 24/7 and       > that is going back to at least 1972.              I would be surprised if you have never experienced a financial       institution operating with a "transaction will be completed       next day" model.              Arne              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca