O
O
Oleg2015-05-05 21:28:23
C++ / C#
Oleg, 2015-05-05 21:28:23

Rust or C++/C?

Should you look into Rust if you want high performance without writing too much code?
What is the purpose of Rust?

Answer the question

In order to leave comments, you need to log in

6 answer(s)
S
Sergey Lerg, 2015-05-05
@wani

The question is not correctly posed. For what purpose do you use language?
I think you can safely choose between Go, Rust, Java and C#. What do you like more.

V
Vladimir Martyanov, 2015-05-05
@vilgeforce

readwrite.com/2011/06/06/cpp-go-java-scala-perform... - work from 2011, C/C++ outperforms Go by 5-7 times even on algorithm with containers.

T
tzlom, 2015-05-21
@tzlom

If there are some small projects, you can take risks and try Rust. Although the language has stabilized (although I won’t be surprised if there are 2-3 more minor changes that are not compatible with 1.0), there are no developments in best practice, objectively the documentation suffers (behind the language) and there is no clear description of all the features folded in one place. The concept of ownership sometimes gets in the way and the usual things are not done as usual.
It's not that Rust is bad, it's still a small community, but let's say I'm personally interested in the language, and started writing a minor project in it - to learn the language and get comfortable with new concepts. Perhaps the implementation of ownership in Rust is not ideal, but I think in the next 5 years we will see both new languages ​​approaching this idea, and add-ons to existing ones that allow us to adopt the advantages of this system, so for myself I singled this out as a target area of ​​​​learning and quietly dig.

O
OnYourLips, 2015-05-05
@OnYourLips

C and assembler.

A
afiskon, 2015-05-06
@afiskon

C++ of course !

M
Mikhail Potanin, 2015-05-14
@potan

The code, in comparison with C ++, will, of course, be reduced, but you won’t be able to win much in development speed. "Ownership" requires more careful thinking, which takes time.
The key feature of Rust is reliability. It’s hard to make a mistake there that requires complex debugging and can crawl into production. So projects with a long life cycle are better to start on it, despite the instability of the compiler. If the program is not planned to be maintained for a long time, then it is most likely more profitable to stay in C ++.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question