4 ms·
For me, it’s mostly because if you have a significant install, there is no clear substitute. I don’t want to migrate 70.000 programs to a new language that wil
by freetanga 6y ago
For me, it’s mostly because if you have a significant install, there is no clear substitute.
I don’t want to migrate 70.000 programs to a new language that will become a fad in 5 years. You cannot rewrite some systems (banking, aerospace, defence, energy,...) from zero every 5-10 years.
- reader_mode 6y agoJava and C# have been industry standard in enterprise for 20+ years now ? There are order of magnitude more trained devs, infrastructure, etc. and risk of getting obsolete in 5-10 years seems negligible. Even then the support community will be order of magnitude greater since so much of existing infrastructure is running those stacks and SW is orders of magnitude greater than it was in COBOL days. You don't need to jump on flavour of the month stack just because you are doing a rewrite.
- rbanffy 6y agoCOBOL is sort of a DSL for business logic. Java and C# are not.
- GoblinSlayer 6y ago>COBOL is sort of a DSL for business logic It was intended to be that, but ended up being a DSL for machine code. The same happened to SQL.