It’s really easy to criticize Rust for being too “strict”. It’s a lot harder to say what specific changes you’d make to make it less strict during development, while still allowing safety during deployment.
-
-
rust has "unnecessary" strictness from pursuing aesthetic goals like being able to "see what code does" / "see expensive operations" / "control everything". swift goes too far, but still demonstrates real rust-relevant conveniences (lifetimes really complicate things though)
-
I think in practice when people talk about Rust strictness they’re 90% referring to lifetimes and the &/&mut restrictions. You’re definitely right that the strict-by-default philosophy pervades the entire language, though.
End of conversation
New conversation -
-
-
I read the "Rust is too strict" idea yesterday. I am not even close to being a compiler writer so forgive me, but couldn't we develop using a GC then do a prod build without one and the compiler would show us everywhere we need to start managing memory?https://twitter.com/Jonathan_Blow/status/1194295021609963521 …
-
Because the memory management scheme fundamentally affects how you write the program. If you try to run a C program through c2rust you’ll see what I mean.
End of conversation
New conversation -
-
-
It would be interesting to see something that does as a language what Ruby devs do in practice: just never free anything during a "request" (whatever that means) and wipe memory in between. Arena allocation writ large, where the only free is to drop a whole arena.
-
Lots of examples of this in the literature, going back to Tofte and Talpin’s ML Kit. That’s classic region memory management. Didn’t catch on, but interesting.
- 1 more reply
New conversation -
-
-
I'm skeptical that betting against improvement is ever a good strategy ;) Rust solves a local maxima for a lot of people, but it seems rather absurd to reject that one can complain about user difficulties in a programming language just because there aren't better alternatives.
-
In other words, we aren't going to reach anything better than Rust if you erase the difficulty people face in using it.
End of conversation
New conversation -
-
-
I'm still relatively new to Rust, but I haven't found it to be too strict, especially after wrapping my brain around the rules of the language. The only problem I have is with the ergonomics of futures, but that's an area I would really want to be strict in development.
-
If anything, I think making it less strict would reduce the appeal of working in the language.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.