← Back to context

Comment by zgs

2 days ago

I don't the fanaticism around memory safe languages. We've had memory safe languages for a very long time. Algol-60, the granddaddy of many modern languages, had it sixty-five years ago. Algol-60 also had other safety features that modern languages don't have - for example integer overflow safety.

The real issue is that we came to accept unsafe languages and are taking a really long time to put such features back.

The real issue is effort. We accept ffmpeg because nobody tried to rewrite ffmpeg in ALGOL-60. We're happy to go through contortions to make ffmpeg or sqlite usable from Java because it's useful and not written in Java and nobody wants to rewrite it in Java.