Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> I also pointed out that Rust has to win the mindshare of C++ programmers first, before even reaching other ecosystems

C++ is just a tool, as is Rust. Rust does not need to win the mindshare of C++ programmers first to become successful. It only needs to itself as a viable alternative in whatever fields people find it useful. I believe it has.

Between WASM, embedded, and even Web development, I see a lot of "mindshare" being attracted to Rust.



Coffeescript also won a lot of mindshare, the point is keeping it for decades.


Coffee Script is a transpiled language and it has become irrelevant when lot of the language features it offered is now natively available in ES6 and up (it has definitely inspired lot of ES6 features like fat arrow functions).

Rust on the other hand is not a thin layer on top of something like Coffee script. So it does not need to keep up with 'something' for decades. As long as it continues to do its current job of making systems programming safer and fun, it is going to be here for a long long time.


I don't think the transpilation was the issue for Coffee Script. After all, most usage of ES6 is through a transpiler anyways. Rather, I think ES6 is simply a superior language to Coffee Script. That's why it has lost marketshare. Likewise, something superior to Rust could arise, and then Rust's marketshare will be in trouble.


As long as it has an OS SDK to make it relevant for tier 1 systems programming.

Meaning coming in Apple, Google, Microsoft, Nintendo, Sony, AMD, NVidia, random IoT OS vendor SDK, with bindings to all relevant OS libraries.

So far, Rust/WinRT seems to be the only thing into that direction, and given how C++/WinRT tooling support turned out, I rather wait and see.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: