Thanks for a comprehensive comparison. > you may find that it's more productive to do work where you're unclear about the object lifetimes in a garbage collect

Thanks for a comprehensive comparison. > you may find that it's more productive to do work where you're unclear about the object lifetimes in a garbage collected language where it isn't your problem. This is exactly why I haven't ventured into Rust yet. But lately I've taken interest in WASM and HW programming. I write in Go-WASM, But have realized that concurrency prowess of Go is irrelevant in WASM as threads are not implemented yet, More over it's a recipe for getting the UI thread blocked. And GC languages are generally a pain on HW with low memory. Is Rust worth the effort for writing WASM? Thereby gaining the necessary skills to apply in HW systems programming?