Re:Compilers are hard
by MaxBarraclough on Thursday January 21, 2021 @07:15AM
(#25858096)
Bit of a nitpick, but the real value is in safe languages, rather than managed languages, no? The distinction is a little blurry, admittedly, but as an example, I figure that verified SPARK counts as safe but unmanaged.
[ Parent
| on HN ]
Because as you might have guessed, I was speaking of iOS, Android and ChromeOS, while SPARK as much as I like it, is a very niche technology.
Re:Compilers are hard
by MaxBarraclough on Thursday January 21, 2021 @07:30AM
(#25858180)
I should have gone with a less niche example: the safe subset of Rust. D also has a safe subset.
Still niche, Rust is not up to the stuff that app developers expect in terms of tooling and D still has quite a few @safe bugs to sort out, among its current adoption issues.
Unfortunely regardless of their own reports regarding CVEs, Microsoft, Apple and Google keep turning to C and C++ for their bottom layers + managed languages, instead of going full speed in some of those alternatives.
So it appears to be the long term solution to mitigate security issues, while keeping compatibility with existing code and tooling.