Re:Async Rust Is A Bad Language
by lmm on Friday September 08, 2023 @11:54PM
(#37442134)
If you're saying you want GC/Arc then that's more than just "turning off the borrow checker".
[ Parent
| on HN ]
Re:Async Rust Is A Bad Language
by throw10920 on Saturday September 09, 2023 @01:43AM
(#37442595)
Pedantry. Later on in my comment I literally say "manage memory for you" - it should be pretty clear that my intent was to talk about a hypothetical language that allowed you to change between use of a borrow checker and managed memory, even if I didn't use the correct wording ("turn off the borrow checker") in that particular very small section of it.
Bit much to complain about pedantry with how prickly your tone has been in this whole thread. If you only want this functionality for rapid iteration/prototyping, which was what you originally said, then leaking memory in those circumstances is not such a problem.
Re:Async Rust Is A Bad Language
by throw10920 on Sunday September 10, 2023 @06:30PM
(#37460778)
My tone has been prickly because of pedantry (like this), blind zealotry, and factually incorrect statements.
> If you only want this functionality for rapid iteration/prototyping, which was what you originally said, then leaking memory in those circumstances is not such a problem.
There's pretty obvious use-cases for wanting your language to be productive outside of prototyping, such as scripting (which I explicitly mentioned earlier in this thread[1]), and quickly setting up tools (such as long-running web services) that don't need to be fast, but should not leak memory.
"Use Rust, but turn the borrow checker off" is laughably inadequate.
Yeah, I do think the space where manual memory management is actually desirable is pretty narrow - and so I'm kind of baffled that Rust caught on where the likes of OCaml didn't. But seemingly there's demand for it. (Either that, or programming is a dumb pop culture that elevates performance microbenchmarks beyond all reason)