Hacker News Reader

Comment by fancyfredbot | Hacker News Reader

There are an awful lot of memory safe languages. For example Python, Java, JavaScript, and the safe subset of C#. Rust just happens to achieve memory safety with a relatively low runtime overhead.

View on HN

The paper specifically eliminates languages with garbage collectors, however.

Seems to specifically include them?

https://media.defense.gov/2023/Apr/27/2003210083/-1/-1/0/CSI...

I was looking at this, which calls it out on page 9. Seems newer, or perhaps the 'can override' clause leaves it unrealisticly open ended?

https://www.whitehouse.gov/wp-content/uploads/2024/02/Final-...

That's specifically for space related software.

Well, planet earth is travelling through space...

The excerpt of the section on memory safety and space that I read seemed to be more concerned with deterministic timing.

Did they address memory corruption?

The description of memory safe languages referenced in the original article(s).

https://media.defense.gov/2023/Apr/27/2003210083/-1/-1/0/CSI...

That's a good point. I was thinking of compiled languages and so wasn't thinking about those.

There are memory safe compiled languages too, e.g. Go or Dart. I think Java and maybe C# can be AoT compiled too these days.

As well as Nim and Swift

Java and C# have been AOT compiled from yearly days as well, the difference to today was for Java AOT compilers were only available in commercial JDKs, and NGEN only supported dynamic linking, while being designed for fast startup times only.

Reply on news.ycombinator.com