I wanted to understand if I am the only one that finds the language hard to understand (primarily it's time system). Am I missing out on something that everyone including junior engineers seems to have figured out.
Ask HN: Are Rust migrations delivering any benefits?
1–6 of 6 posts
Re: Ask HN: Are Rust migrations delivering any benefits?
#2But ultimately you can use any language you want and you don’t need to do anything just because other people are doing it. Do what makes sense for your project.
Re: Ask HN: Are Rust migrations delivering any benefits?
#3It can be difficult to separate the benefits of rewriting in Rust with the benefits of rewriting in general. But you can get the most benefit by structuring your code in a way that forces its correctness to be validated at compile-time, where possible. You can limit a lot of bugs and programmer mistakes this way, as well as better reason about the code. But ultimately you can use any language you want and you don’t n…
Can you elaborate this more?
Re: Ask HN: Are Rust migrations delivering any benefits?
#4Re: Ask HN: Are Rust migrations delivering any benefits?
#5With C or C++, implementing a simple tree structure is straightforward, but in Rust, even writing a linked list is painful. The ecosystem is also fragmented. Most people use Tokio, and while AI can solve a lot of problems, AI often generates bad code just to work around the Borrow Checker.
That said, the UX experience is good—but the developer experience is terrible, and there's so much to learn. Things that would just work in other languages require explicit handling in Rust. A lot of people like Rust's technical purity, but I don't like it because of the terrible experience that comes with it.
That said, if I had to rewrite a large project from scratch, I think I would choose Rust. The benefits are that big.
Personally, I think it has both pros and cons