Ask HN: Why do you use Rust, when D is available?

Re:Ask HN: Why do you use Rust, when D is available? by calaphos on Friday June 12, 2020 @07:08AM (#23498053)

Rust is very very new compared to Cpp. People have decades of experience with cpp, learned in in University. Why would you throw all of that overboard just to learn a fancy new language with a weird ownership system? Keep in mind that people often still write cpp98 and have a rely hard time getting used to newer cpp concepts and programming styles. And all of that is backwards compatible with their existing codebase.

[ Parent | on HN ]

Re:Ask HN: Why do you use Rust, when D is available? by Aeolun on Friday June 12, 2020 @07:43AM (#23498246)

> Why would you throw all of that overboard

Firstly, because 75% of all that knowledge is easily transferrable.

Secondly, because you want to take 50% of your bug count.

[ Parent | on HN ]

Re:Ask HN: Why do you use Rust, when D is available? by zucker42 on Friday June 12, 2020 @11:03AM (#23499947)

He was saying this in the context of "why do people still use C++ at all".

[ Parent | on HN ]

Re:Ask HN: Why do you use Rust, when D is available? by bjourne on Friday June 12, 2020 @09:11AM (#23498846)

But why not program in Python and take 100% of your bug count?

[ Parent | on HN ]

Re:Ask HN: Why do you use Rust, when D is available? by UncleMeat on Friday June 12, 2020 @10:44AM (#23499709)

It is slow.

It doesn’t work well for embedded programming.

It very much does not fix all bugs, especially given lack of static type checking.

[ Parent | on HN ]

Re:Ask HN: Why do you use Rust, when D is available? by dpc_pw on Friday June 12, 2020 @05:08PM (#23503942)

It will sound harsh, but people who can't up their game from C++98 to C++11, are probably not a people that I would consider hiring anyway. Generally, personally I would not hire anyone that knows just one programming language that they've learned in University and for years didn't manage to practice anything else, but that's just me.

I actually worked in Automotive, and the software higher level up the stack there is usually god damn awful piece of s*, often done by people who have almost no clue what they are doing, with plenty of misconceptions about how C/C++ even really works (using `volatile` for concurrency/atomicity and stuff like that). They are just beating their spaghetti code from segfault to segfault for decades.

This and slow delivery process easily explains why entertainment, navigation and other software-driven part of mainstream cars are so buggy, slow and generally terrible, and why Tesla could have so easily deliver way better experience.

So it doesn't matter that some people can't "get into Rust". The business that hire them will be replaced if they can't up their game, that's all.

[ Parent | on HN ]

Re:Ask HN: Why do you use Rust, when D is available? by MacSystem on Wednesday June 17, 2020 @03:07PM (#23555412)

If D have had a proper tooling, like C# and VS, do you think companies in the automative would consider to use D instead of C++?

[ Parent | on HN ]