5 ms·

It's hard to not respect the devotion and love Rustaceans give to Rust.

by kanobo 6y ago

est31 6y ago
Not the author, but the reasons that brought me to Rust from C++ 5 years ago are still valid today. Consistent build system supporting an online repo (cargo), safety, C++ best practices encoded as compiler lints, consistent naming policy. The last one seems innocuous but it's actually really annoying to integrate multiple libraries with different naming styles, having to remember when to use PascalCase vs _.
- Ygg2 6y ago
  Don't forget a hyper friendly compiler, with helpful error messages.
  - cft 6y ago
    I feel that it's a future of compilers: it almost feels like in interactive session, where you can actually learn stuff. I suggest expanding this.
    - rowanG077 6y ago
      Have you heard of Idris? It's tagline is programming as a conversation.
  - cletus 6y ago
    To be fair--and I say this as a Rust fan--the pages of inscrutable error messages caused by a misplaced parenthesis in a template are pretty much over. Clang spearheaded this change to the point where some companies would use clang for development and gcc for production builds. This isn't to say that template errors are problem-free but the situation is much better than it was 5 years ago.
    - Ygg2 6y ago
      I didn't mean it as slight against C++ template errors. Java is my daily professional development. That's the baseline. And it's errors are not good as Rust's. I often joke that IntelliJ IDEA is better programmer than I am. But in Rust, the same can be said of the Rust compiler. The amount of suggestions, and explanations is stellar.
      - jfkebwjsbx 6y ago
        But you were adding to the parent's list, which was giving reasons to move from C++ to Rust.
        Ygg2 6y ago
        I said, don't forget as in extra reasons to prefer it. It was 100% unrelated to C++ errors.
  - adsjhdashkj 6y ago
    It's so helpful that it's jarring when it's not - hah. Ie, i tried out Diesel for a few projects and after several months, i'm moving away from it. The compiler messages can be insane due to Diesel's rather.. excessive use of generics haha.
    - anw 6y ago
      Just curious, but what are you replacing diesel with?
      - adsjhdashkj 6y ago
        SQLx - unfortunately using some blocking wrappers for (currently) some non-async codebases. SQLx has been really nice so far. I recommend it.
- CommieDetector 6y ago
  Rust SIMP detected
Tade0 6y ago
It's hard to not love a language the compiler of which uses words like "perhaps" in error messages, suggesting solutions that are often what you wanted to do in the first place. I've been writing in Rust in a very on-and-off fashion and thanks to the compiler messages I'm able to pick up where I left even after a few months. All that while being a front-end developer or, in other words, as far removed from systems programming as possible.

It's hard to not respect the devotion and love Rustaceans give to Rust.

by kanobo 6y ago

It's hard to not respect the devotion and love Rustaceans give to Rust.

Not the author, but the reasons that brought me to Rust from C++ 5 years ago are still valid today. Consistent build system supporting an online repo (cargo), safety, C++ best practices encoded as compiler lints, consistent naming policy. The last one seems innocuous but it's actually really annoying to integrate multiple libraries with different naming styles, having to remember when to use PascalCase vs _.

Ygg2 6y ago
Don't forget a hyper friendly compiler, with helpful error messages.
- cft 6y ago
  I feel that it's a future of compilers: it almost feels like in interactive session, where you can actually learn stuff. I suggest expanding this.
  - rowanG077 6y ago
    Have you heard of Idris? It's tagline is programming as a conversation.
- cletus 6y ago
  To be fair--and I say this as a Rust fan--the pages of inscrutable error messages caused by a misplaced parenthesis in a template are pretty much over. Clang spearheaded this change to the point where some companies would use clang for development and gcc for production builds. This isn't to say that template errors are problem-free but the situation is much better than it was 5 years ago.
  - Ygg2 6y ago
    I didn't mean it as slight against C++ template errors. Java is my daily professional development. That's the baseline. And it's errors are not good as Rust's. I often joke that IntelliJ IDEA is better programmer than I am. But in Rust, the same can be said of the Rust compiler. The amount of suggestions, and explanations is stellar.
    - jfkebwjsbx 6y ago
      But you were adding to the parent's list, which was giving reasons to move from C++ to Rust.
      - Ygg2 6y ago
        I said, don't forget as in extra reasons to prefer it. It was 100% unrelated to C++ errors.
- adsjhdashkj 6y ago
  It's so helpful that it's jarring when it's not - hah. Ie, i tried out Diesel for a few projects and after several months, i'm moving away from it. The compiler messages can be insane due to Diesel's rather.. excessive use of generics haha.
  - anw 6y ago
    Just curious, but what are you replacing diesel with?
    - adsjhdashkj 6y ago
      SQLx - unfortunately using some blocking wrappers for (currently) some non-async codebases. SQLx has been really nice so far. I recommend it.
CommieDetector 6y ago
Rust SIMP detected

Tade0 6y ago

It's hard to not love a language the compiler of which uses words like "perhaps" in error messages, suggesting solutions that are often what you wanted to do in the first place. I've been writing in Rust in a very on-and-off fashion and thanks to the compiler messages I'm able to pick up where I left even after a few months. All that while being a front-end developer or, in other words, as far removed from systems programming as possible.