3 ms·
Is this an outlier or has Rust started to be part of the establishment and being 'old' so that people want to share their "moving away from Rust" stories? I di
by bulbar 7mo ago
Is this an outlier or has Rust started to be part of the establishment and being 'old' so that people want to share their "moving away from Rust" stories?
I didn't mind reading articles that are not about how Rust is great in theory (and maybe practice).
- quotemstr 7mo agoThere's a certain segment of the industry that's always chasing the newest thing. Many of them like Zig for some ghastly reason. That said, Rust does have real problems. Manual memory management sucks. People think GC is expensive? Well, keep in mind malloc() and free() take global locks! People just have totally bogus mental models of what drives performance. These models lead them to technical nonsense.
- zozbot234 7mo agoThis story is about moving away from WASM for an application that's unsuitable for it. It's not really about Rust.
- notnullorvoid 7mo agoIt's not an unsuitable application for WASM. They could've drastically reduced the WASM boundary impact if instead of mapping to JSON in Rust they streamed out structured bytes to JS then mapped to JSON there. And the streaming fix was language independent. So it's more so a story about architectural mistakes.