Rust Is Hard, Or: The Misery of Mainstream Programming
hirrolot.github.io
Rust Is Hard, Or: The Misery of Mainstream Programming
1–10 of 811 posts
Re: Rust Is Hard, Or: The Misery of Mainstream Programming
#2Re: Rust Is Hard, Or: The Misery of Mainstream Programming
#3Re: Rust Is Hard, Or: The Misery of Mainstream Programming
#4Re: Rust Is Hard, Or: The Misery of Mainstream Programming
#5Re: Rust Is Hard, Or: The Misery of Mainstream Programming
#6Rust isn't hard. Programming is hard. Rust just points out failure states before you encounter them in production.
Some of what the author is complaining about matches my conversations with people who aspire to be Rust library authors — that you're often trying to hijack the type system because you actually know better.
Re: Rust Is Hard, Or: The Misery of Mainstream Programming
#7Re: Rust Is Hard, Or: The Misery of Mainstream Programming
#8Some observations:
- The compiler is always right.
- Do what clippy and rust-analyzer says. Don't ask questions.
- If you're fighting the compiler, clippy, AND rust-analyzer, then you're almost definitely wrong.
Virgins try to use &str everywhere. Chads just use String.
Re: Rust Is Hard, Or: The Misery of Mainstream Programming
#9Rust isn't hard. Programming is hard. Rust just points out failure states before you encounter them in production.
The narrative that "Rust isn't hard" is getting tiresome, and I say this as someone who writes a lot of Rust. Let's be honest that Rust can be harder than many other programming languages in many ways, but those of us who use it believe the upsides and tradeoffs are worth the minor to moderate increase in difficulty.
Pretending Rust is easy just sets beginners up for disappointment when they get into Rust and realize it wasn't what they were sold. Or worse, they start doubting themselves when they encounter the hard parts because Rust fans were busy insisting it's all easy.
Re: Rust Is Hard, Or: The Misery of Mainstream Programming
#10I care about speed and correctness but Rust makes me also care about ownership and lifetimes even when I don't really want to care about that stuff. I've written Rust for years now and this still occasionally can really slow me down. Rust is still a very nice language so I just deal with it :) no pain no gain.
I would love a Rust-with-GC or something in that spirit that is similar to Rust but automatically figures out lifetimes as much as possible and GCs whatever it cannot figure out automatically. I've looked at languages like Nim and read about research languages like Koka so I'm optimistic something will emerge from this space I really like.