4 ms·
> You're smarter than Rust. I'm not kidding! You're probably not. That's kind of the thing. Rather, it's not that you're not smarter, it's just that you're not
by arcticbull 6y ago
> You're smarter than Rust. I'm not kidding!
You're probably not. That's kind of the thing. Rather, it's not that you're not smarter, it's just that you're not used to doing things properly, and Rust forces you to do things properly.
"Leave me alone, I know what I'm doing" says beginner juggling chainsaws on a unicycle.
Ultimately it comes down to this: when you don't write down all the information a compiler needs to generate an artifact, you're relying on hidden, un-stated assumptions. Such assumptions are subject to change over time. Relying on them isn't smart, it's dumb. It makes you feel smart. Just check the CVE list.
- heldrida 6y agoThe original writer is trying to make it appealing for beginners; there are rules, you can learn, you are smart! He's very positive and encouraging, which shows how much dedication he puts on his teachings. Relax
- arcticbull 6y agoOh, sorry for the confusion, I wasn't criticizing, I really enjoyed the article. I'm working with someone new to Rust at the moment and I'm passing it along to them, too.
- heldrida 6y agoThat's fine, happens with all of us! Just that we need to be positive, in the end... we are all trying to figure it out, be it Rust...or CSS ;)
- dragonsh 6y agoAnother example from Rust community, without reading the article commenting that Rust is always correct without any bugs or error and programmer is stupid. This attitude continuously drives me away from learning Rust, didn’t find such attitude in Haskell or Lisp community which really took computer science and art of programming forward unlike Rust, which is similar to other competing niche languages.
- arcticbull 6y agoTo be clear, that isn't what I meant, though I can't really edit my comment for clarity. Some things don't manifest the way you intend when converting from thoughts to text.
- doonesbury 6y agoSometimes I get the impression from rust advocate articles on HN that they are snobs. Not here; no way. This was well written, cheeky, thorough, and gave me a solid sneak peak at doing rust from a c/c++/go/python/Java background. The exacting standards of stopping data races at compile time is an exacting task. I think I followed most everything here, although I wondered if the crossbeam inclusion should be in language not library code ... But I don't know enough to press further. Solving problems in libraries not language probably is better. Rust is one of few if only languages I am aware of that hit hard on data safety without a gc. That'll make it quite different to the programmer.
- fasterthanlime 6y agoI'm happy you enjoyed the article! I seem to remember scoped threads were part of the standard library at some point, but they were eventually proved unsound and removed. I'm too lazy to go find a reference right now but it shouldn't be overly hard.
- avasthe 6y agoThese zero information statements and intellectually dishonest marketing is what keeps rust a fringe language. > it's just that you're not used to doing things properly, and Rust forces you to do things properly. Many patterns that rustc refuses aren't inherently wrong. They are because 1) you have to aid lifetime inference and memory management unlike GC languages 2) All safe patterns can't be verified by compiler, especially if threads are involved. The cult like mentality of rust spammers on hackernews is making many people sceptic about it. Rust is actually well designed language for what it does. But stop pretending rust is God.
- arcticbull 6y ago> Many patterns that rustc refuses aren't inherently wrong. They are because 1) you have to aid lifetime inference and memory management unlike GC languages 2) All safe patterns can't be verified by compiler, especially if threads are involved. It's not about the patterns being wrong, it's about the patterns being verifiable and having a compiler that's on your side, not on the side of watching the world burn. The difference between C's laissez-faire approach, where no new warnings are added and anything's whatever you want it to be vs. a subset of provably correct things you can opt out of at your discretion. Yes, it's not going to catch all edge cases, yes it's not perfect, however the idea people are behind is that it represents a fundamental change from "I'm sure the smart engineer knows what they're doing" to "hold on now, let's assume they don't, or will forget in 6 months, or some new person is going to have zero context." That model maps much better to the reality we have vs. the one we wish we had. My opinion is hardly culty, I write ObjC at my day job at $BIGCO, I've done plenty of Swift, I've written plenty of embedded C, plenty of C++, implemented a ton of stuff in VHDL. Rust is my go-to for personal projects. It's genuinely better. Not perfect, better. And better's what I'm looking for.
- moldavi 6y agoIve always wondered something: comparing to languages like Swift, is Rust really better if it takes so much cognitive overhead and architectural backflips to work around the borrow checker's limitations? Couldnt we be spending that time adding features, or optimizing the parts of the program that the profiler shows us are inefficient? Using Rust seems like it would make sense for an extremely low-level performance-sensitive application, but do people use it for higher level things? If they do, why?
- blub 6y agoActually this is not a matter of smartness and paying attention. Real world projects expanding over years and decades behave like complex systems and it can be guaranteed that they will have correctness issues. Furthermore there's always a tension between speed and safety in C and C++ programs which make them particularly prone to these errors. In fact there are probably many people who are competent enough to write safe C++ code (C's a lot harder), but they code in environments where this is unlikely to happen.