Post AFe9ZtGdIFl0eyay80 by Seirdy@pleroma.envs.net
 (DIR) More posts by Seirdy@pleroma.envs.net
 (DIR) Post #AFe2NJHKZcaft9yZ9s by mansr@society.oftrolls.com
       2022-01-20T21:59:19Z
       
       0 likes, 0 repeats
       
       @lattera @rysiek I'm expecting to see many more of these kinds of bugs as people rush to reimplement mature tool and libraries in Rust or another "safe" language.
       
 (DIR) Post #AFe7xTyelxalGZJDMW by Seirdy@pleroma.envs.net
       2022-01-20T23:01:54.186547Z
       
       0 likes, 0 repeats
       
       @lattera Yes. Memory safe languages are memory safe, not everything-safe. Memory safety is one of many important steps in the right direction.
       
 (DIR) Post #AFe9ToFt109ZNULY7k by loweel@boseburo.ddns.net
       2022-01-20T23:07:06.487448Z
       
       0 likes, 0 repeats
       
       @Seirdy @lattera then use ADA. It's much more safe than rust
       
 (DIR) Post #AFe9TojJFbgmqk72zA by Seirdy@pleroma.envs.net
       2022-01-20T23:18:56.083583Z
       
       0 likes, 0 repeats
       
       @loweel @lattera This isn't true out of the box if you start introducing concurrency and parallelism. Borrow-checking handles whole classes of bugs including races.Personally I'd rather use Zig when I'm not doing stuff that's too racy for tests to handle. Rust's single-implementation and feature creep are concerning to me, but it is head and shoulders above other langs with manual memory management and even several GC languages (e.g. Go, another one of my favorites) when it comes to memory safety and especially race detection.
       
 (DIR) Post #AFe9ZtGdIFl0eyay80 by Seirdy@pleroma.envs.net
       2022-01-20T23:20:02.469654Z
       
       0 likes, 0 repeats
       
       @lattera Correct. We should eliminate what we can eliminate, within the constraints we're given.