What it feels like when Rust saves your bacon

Re:What it feels like when Rust saves your bacon by proto_lambda on Friday June 24, 2022 @07:00AM (#31860024)

One big hurdle for C++ programmers learning Rust that I've seen time and time again in various community support channels is fixing their trust issues with the compiler. They are so used to compiler output being useless or worse than useless, they are unable to take advantage of rustc's stellar diagnostics (which frequently tell you exactly what you need to change to make things work) until they force themselves to actually read and internalise them.

Once they realize that the tooling is actually working _with_ them, not _against_ them, they start to pick things up much quicker.

[ Parent | on HN ]

Re:What it feels like when Rust saves your bacon by scoutt on Friday June 24, 2022 @11:00AM (#31863183)

> big hurdle

Without going much further, to me it's the syntax. I can write some Rust lines of code, and I appreciate the compiler output to correct my syntax. But it's really difficult to me to read code written by others. I can't open a random file of a Rust project and have a minimal clue of what's going on

After years of C and some C++, I have a parser implanted in my cerebellum, and it's hard to adapt it to Rust. To me, reading Rust feels like forcing an optical nerve to see something very small.

Case in point, the code in this article.

[ Parent | on HN ]

Re:What it feels like when Rust saves your bacon by bilkow on Friday June 24, 2022 @01:57PM (#31866658)

Oh yeah, I feel your pain, my brain is really used to Rust/Swift and Python syntax, and when I have to read Typescript/React, C++ or something like Nix, it gets hard for my brain to parse it. Loved the eyesight analogy!

[ Parent | on HN ]

Re:What it feels like when Rust saves your bacon by lionkor on Friday June 24, 2022 @08:54AM (#31861021)

In my experience only beginners have this issue, as a C++ programmer the compiler is my best friend.

[ Parent | on HN ]