jckarter

everyone already knows i'm a dog

the swift programming language is my fault to some degree. mostly here to see dogs, shitpost, fix old computers, and/or talk about math and weird computer programming things. for effortposts check the #longpost pinned tag. asks are open.


email
mailto:joe@duriansoftware.com
discord
jckarter

Catfish-Man
@Catfish-Man

This is why: https://security.googleblog.com/2022/12/memory-safe-languages-in-android-13.html

Yes, it's about languages that aren't Swift, on a platform I don't work on, but the same principles apply. Up until now nothing we've done as an industry has really made a dent in these problems, and we've been trying really hard. Memory-safe systems languages won't solve every problem, but we finally have a weapon in a fight we've been losing horrifically.

(also, huge kudos to my Rust friends, this is an amazing validation of y'all's work!)


You must log in to comment.

in reply to @Catfish-Man's post:

it's really weird thinking of memory vulnerabilities as something that has an end point. They've been with us since the dawn of computing, consistently. It's going to be like eliminating smallpox, or maybe a little more like polio since we're still leaving openings, but only in crucial areas where they can be watched. Still, it's going to go from omnipresent down to handfuls of cases. I have some mixed feelings about this, relating to companies being able to keep better control of devices they produce, keeping capabilities locked away from end users, but that doesn't really outweigh the massive benefits in other areas.

oh definitely. We had a really great discussion about this on a Discord I'm on a few days ago. One of our more idealistic type theorists had an eye opening and upsetting introduction to the idea that software correctness can be authoritarian. I feel like anyone who grew up with (or with stories of) "hacker culture", phreaking, warez, DeCSS, demoscene, circuitbending/bitbending/glitch art, etc… will understand this intuitively.