I swear to god, companies are nowadays just picking the solution with the most buzzwords. Any compiler engineering student knows how to write a transpiler from one language to another, while getting this right is a cumbersome task, it still completly automated afterwards. Just hire a few compiler engineering phds and the job is done in at least half a year.

Look what i found after a quick google search:

[–] [email protected] 49 points 11 months ago (2 children)

You want to translate COBOL to another language? That exists as a commercial product! The complexity is not the syntax though, it is the environment and subsystems surrounding the code. A lot of COBOL is designed for mainframe systems, and emulating a mainframe is complex.

You also end up with code that is still written as if it were COBOL. The syntax for COBOL is the easy part and that is all you can easily replace. Afterwards you're still stuck with the way of working and mindset, both of which are quite peculiar.

The company I work for recently looked at all of this, and we decided not to translate our code.

[–] [email protected] 6 points 11 months ago (3 children)

Also, isn't COBOL extremely fast ? Which is not necessarily true for newer languages

[–] [email protected] 7 points 11 months ago

Rust: am i a joke to you?

[–] [email protected] 4 points 11 months ago

I think that's mostly because of the systems COBOL usually runs on, not so much because of the language

[–] [email protected] 3 points 11 months ago

You're probably thinking of Fortran, which is still used for hardcore number crunching in areas like physics.

[–] [email protected] 4 points 11 months ago* (last edited 11 months ago) (1 children)

Just make the devs learn the language if they don’t know it already. What kind of shitty mid to senior dev can’t learn a new language in a reasonable amount of time.

[–] [email protected] 4 points 11 months ago* (last edited 11 months ago)

I think it's a matter of expertise. I am stuck dealing with people who write Javascript/Typescript like it's C# because they're C# senior devs. It's not world-ending until issues of speed, scale, or other "why we use best practices" raise their ugly heads. Then it is world-ending. I can only help with so many design standards when you still see everything show up in a classes-and-subclasses mindset with hard-to-catch concurrency bugs. I actually caught a developer trying to spin up a child process to wait on a socket response.

So in FinTech, I can imagine it becomes a bigger deal faster.