Convert me to Rust

Stop creating these threads.

>>59591702

Why eating apples, when oranges or peaches are a thing?

Go is nice for small and fast servers or some simple concurrency.

Rust is still pretty immature, I'm pretty sure it will have a bright future, but for the next two years there won't be any jobs.

C++ is battle proven and the de facto standard in some areas. Even if tomorrow nobody would make new C++ projects, there would still be a gorillion of legacy projects that want to get maintained.


So this is how you should do it:

1. Learn C. Even if you only work yourself through K&R in two months, it's worth it. Everybody knows C, it's so mandatory it's not even funny.

2. If you know C (not only the syntax, but have done some projects), you can learn Go in a few days. It's basically "C for noobs with concurrency included", but learning Go first will make C kinda difficult to understand for you. Also C is present for a lot of fields, while Go is pretty much centered about internet backends.

3. If you know C, then take a look at C++. Either you need it or you don't, the jobs are pretty clear for C++. It's a pretty big and complex language, but the basics are not that difficult. Just give it a shot and see if you like it.

4. Rust is more a thing for some side projects. If you are good in C (or better: in C++) and find a Rust job - good for you! But chances are that you might only use it for yourself for a long time. Nothing wrong with Rust, it's interesting and fresh, but not important yet. Industry moves slowly.


> tl;dr: learn them all, start with C

File: download (14).png (5KB, 318x159px) Image search: [Google]

5KB, 318x159px

>>59591702
None. I've heard that its better than C in some aspects but that the community is the most toxic SJW infested thing in the entire internet

>>59591962
I know C, Python, quite a bit of Golang, Asm, VHDL, quite a bit of C++, polyml,. Clisp, and Java. Rust seems quite intuitive so far, except for some notations. It's either Rust or Haskell now.

>>59592729

That's a different story then..

Haskell and Rust are both worth learning, but for different reasons. They are totally different.

Haskell is one of the most beautiful languages out there, and of course it's functional. A totally different paradigm that will make you think about your code.

Rust is more like a nicer version of C++ without all that magic.

So the choice is more about:
You want to become a better, more well-rounded programmer? --> Haskell
You want to go close to metal and make high performance shit but you don't like C/C++ anymore? --> Rust