If I was writing no-alloc production code, I would stick with Rust, FWIW, at least until Go's library ecosystem improves. I don't mind writing Rust (have been

If I was writing no-alloc production code, I would stick with Rust, FWIW, at least until Go's library ecosystem improves. I don't mind writing Rust (have been dabbling with it since ~2014), especially with some AI assistance. It's just more of a grind for me than working with Go. > Considering the effort involved in coding in such unnatural Go variant, I was also expecting writing Go in this style to be more friction, but it was surprisingly smooth. The friction was entirely from lack of libraries and a little uncertainty about how to communicate errors without allocating. Rust has better libraries by far, but I felt more friction from the language (e.g., if you have a buffer you have to initialize every element of it or you have to use something like `heapless::Vec`--not a big deal, just decisions to make to figure out what the happy path is).