News for hackers. Stuff that matters.
Re:Memory Safe Languages in Android 13 by cesarb on Thursday December 01, 2022 @03:51PM (#33822533)
> It has unsafe escape hatches (via ffi, at the very least).

Playing devil's advocate, I can think of at least one language which has no escape hatches: Javascript running within a web page.

Re:Memory Safe Languages in Android 13 by burntsushi on Thursday December 01, 2022 @04:53PM (#33823430)
Yes, but that's not just a language. It's a language within a certain context. But it is a worthy mention.
Re:Memory Safe Languages in Android 13 by kaba0 on Friday December 02, 2022 @02:46AM (#33827942)
It is very easy to create a safe language. Hell, most brainfuck interpreter is likely completely safe, you allocate a large enough array and just iterate over its basic instructions that only ever modify that array and print a character. A Turing machine in itself can do no harm.

The hard part comes at allowing it to do something useful, but only the parts I believe should be able to. E.g. plugging in file system access to our brainfuck interpreter will make it quite unsafe. Node for example does have C FFI.