How an Engineering Company Chose to Migrate to D

Re:How an Engineering Company Chose to Migrate to D by protocode on Wednesday June 20, 2018 @05:13PM (#17359832)

C still has it's place. It's not glamorous, but it works. COBOL has no decent replacements. Yet. Some have tried. Almost all have failed. Old does not mean useless. If it works, then it's not wrong.

[ Parent | on HN ]

Re:How an Engineering Company Chose to Migrate to D by pjmlp on Thursday June 21, 2018 @01:54AM (#17362473)

On UNIX clones and embedded developers that won't take anything else even at point gun.

.NET, Java are good COBOL replacements.

http://www.fujitsu.com/global/products/software/developer-to...

https://www.microfocus.com/products/visual-cobol/

[ Parent | on HN ]

Re:How an Engineering Company Chose to Migrate to D by coldtea on Thursday June 21, 2018 @04:16AM (#17363097)

>.NET, Java are good COBOL replacements.

Not even close.

As for the links, those are still about COBOL the language.

[ Parent | on HN ]

Re:How an Engineering Company Chose to Migrate to D by pjmlp on Thursday June 21, 2018 @04:32AM (#17363176)

I guess you need to inform yourself about migration projects that use those products to bring COBOL codebases to modern platforms, where new features are then written in Java/.NET languages, while the old working code is left as is.

[ Parent | on HN ]

Re:How an Engineering Company Chose to Migrate to D by coldtea on Thursday June 21, 2018 @08:11AM (#17364351)

Nobody argued that new features could be "written in Java/.NET languages".

Not even that COBOL codebases could be bridged and work "left as is" alongside those.

The main objection was with the word "good".

[ Parent | on HN ]

Re:How an Engineering Company Chose to Migrate to D by pjmlp on Thursday June 21, 2018 @08:26AM (#17364442)

Except you have your definition of "good" and I have mine.

This statement is meaningless without additional information.

> COBOL has no decent replacements.

[ Parent | on HN ]