Live data from Hacker News

How an Engineering Company Chose to Migrate to D

dlang.org

91–100 of 170 posts

Re: How an Engineering Company Chose to Migrate to D

#92

Earlier quoted context omitted.

The biggest problem is they have engineers who have turned their hands to programming, one would expect, without the formal training and so have latched onto various antipatterns without knowing any better because Pascal allowed them to get away with it - painting themselves into a corner. He mentioned an awful lot of code that would have to be refactored, and it could be that they are just too far down the rabbit ho…

Given they started in the 80's Pascal probably has fewer corners to paint oneself into then many languages then (and now probably).

Indeed!

Re: How an Engineering Company Chose to Migrate to D

#93
post #24

While the article states that other languages were evaluated, it seems as though the project was motivated entirely by the author and the evaluation was just paying lip service to what was basically a foregone conclusion. Don't get me wrong, I like D from the small amount of playing I've done with it -- and maybe it is the best tool for their purposes -- but this doesn't strike me as an impartial evaluation. The need…

> If it's just for the sake of one-to-one transpilation, then I can see the point, but a refactoring exercise seems like a better effort to make than language migration. I think the author makes it clear that direct conversion from Pascal is the primary goal. I'm guessing that once the codebase is fully transpiled to D, refactoring would be the logical next step.

Confirmed.

Re: How an Engineering Company Chose to Migrate to D

#94

Earlier quoted context omitted.

Just tell your new hires here is a book on the language go learn it - which is what I was told at my first Job (world leading RnD).

I am usually not against learning new stuff. But I would also like my learning from current work generalize to my future career. From a pragmatic perspective, learning D is probably going to have less ROI. Either the company focus solely on finding enthusiasts or they pay the premium to overcome this.

True up to a point but any professional developer needs to be able to pick up a new language quickly - I had to learn Pl/1G to work on a Map reduce code base.

I was assuming a more rational choice but then developing serious technical software in pascal instead of fortran in the 80's was not a rational choice in the first place.

Re: How an Engineering Company Chose to Migrate to D

#96

Really cool to see companies willing to migrate to a more modern language. I'm part of a team working on C to Rust migration tools (partly inspired by the Corrode translator). Shameless plug/pre-alpha demo: https://www.c2rust.com Edit: missing word.

Your SSL certificate works in Chrome, but not in my Safari 11.1.1. SSL Shopper (not sure how reliable this is), also shows warnings.

https://www.sslshopper.com/ssl-checker.html

Re: How an Engineering Company Chose to Migrate to D

#97
post #88

While the article states that other languages were evaluated, it seems as though the project was motivated entirely by the author and the evaluation was just paying lip service to what was basically a foregone conclusion. Don't get me wrong, I like D from the small amount of playing I've done with it -- and maybe it is the best tool for their purposes -- but this doesn't strike me as an impartial evaluation. The need…

>The need for nested functions bugged me as well. That seems like an odd deal-breaker and hints at code smell Nested functions were a very common pattern on languages like Pascal, Modula or oberon. They are equivalent to code blocks inside a function in C.

The equivalent in C is code blocks connected with gotos. In my conversions of C code to D, I'm able to replace these gotos with nested functions, which makes the code significantly easier to read.

Re: How an Engineering Company Chose to Migrate to D

#98

While the article states that other languages were evaluated, it seems as though the project was motivated entirely by the author and the evaluation was just paying lip service to what was basically a foregone conclusion. Don't get me wrong, I like D from the small amount of playing I've done with it -- and maybe it is the best tool for their purposes -- but this doesn't strike me as an impartial evaluation. The need…

> (Also, don't Rust and Go have closures? Surely that would satisfy this requirement.) Indeed they do. It's completely unclear why they don't satisfy the OP's requirement.

To be frank: I have never used Rust nor Go. Nevertheless, I am quite sure closures and goroutines would complicate the translation due to different syntax from ordinary functions. The same argument is being discussed at reddit https://www.reddit.com/r/programming/comments/8si75b/how_an_...

Re: How an Engineering Company Chose to Migrate to D

#99

While the article states that other languages were evaluated, it seems as though the project was motivated entirely by the author and the evaluation was just paying lip service to what was basically a foregone conclusion. Don't get me wrong, I like D from the small amount of playing I've done with it -- and maybe it is the best tool for their purposes -- but this doesn't strike me as an impartial evaluation. The need…

Framing closures as a “requirement” is pretty strange. Depending on the context they can be an ergonomic nice-to-have, but it’s not like you can’t express a program without them.

A language with only goto and call statements can express any program, too. It's not unreasonable to require higher level programming constructs, because such make programming faster and less prone to error.
Post reply on HN