3 ms·
https://news.ycombinator.com/item?id=43413702 https://news.ycombinator.com/item?id=43413702 is one example. A Rustacean implied Go was not memory safe and that
by hitekker 2y ago
https://news.ycombinator.com/item?id=43413702 https://news.ycombinator.com/item?id=43413702 is one example.
A Rustacean implied Go was not memory safe and that Microsoft couldn't understand the power of Rust. Steve Klabnik & others told them off. But other Rustaceans, like Patrick Walton, argued that Go has memory safety issues in theory.
- neonsunset 2y agohttps://dictionary.cambridge.org/dictionary/english/abuse https://dictionary.cambridge.org/dictionary/english/abuse Rustacean, Gopher... this is an embarrassing way of looking at it. And, speaking of, Go is not a memory safe language when you reach for its concurrency primitives as it very easily lets you violate memory safety (as opposed to Rust, .NET and JVM, where instead you get logic bugs but not memory safety ones).
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]