Re:Eliminating Memory Safety Vulnerabilities at the Source
by pdimitar on Thursday September 26, 2024 @05:59AM
(#41656497)
It's impractical to increase the surface of complexity even further. I for one approve that they settled on just one memory-safe language for their new code.
[ Parent
| on HN ]
Re:Eliminating Memory Safety Vulnerabilities at the Source
by _ph_ on Sunday September 29, 2024 @07:02AM
(#41686513)
Oh sure, for the Linux kernel, Rust makes a lot of sense and one would try to keep the number of languages used minimal. But I was speaking about an abstract context. There are plenty of memory safe languages which could be used. But eventually, one has to decide for one.