Can't wait for my copy of "Advanced Topics in Types and Programming Languages" to come in
yosh
Posts
-
Can't wait for my copy of "Advanced Topics in Types and Programming Languages" to come in -
Memory safety in programming languages is honestly table-stakes at this point.I don't think I'm saying anything particularly new here. But sometimes I just feel the urge to say this out loud. Because I do think it's important.
-
Memory safety in programming languages is honestly table-stakes at this point.Almost non-intuitively: I do love memory unsafe languages as well, and I believe researching these and developing these is immensely valuable!
Just not… entire high-level languages. Assembly and Intermediate Representations are all often not memory-safe. And a lot of languages also have memory-unsafe subsets of languages that need good semantics (e.g. unsafe Rust, Python FFI, etc.)
-
Memory safety in programming languages is honestly table-stakes at this point.Like: if someone wants to build a language called "oops all pointers" I think that's cool and they should do it. Like, get nutty with it.
But writing a web server in it that brokers access to private data feels akin to vocational malpractice. Part of the blame, of course, lies with the person choosing to do that. But if all of the language's examples are of networked applications, I think they are responsible too.
-
Memory safety in programming languages is honestly table-stakes at this point.Memory safety in programming languages is honestly table-stakes at this point. If a new (high-level) programming language can't even meet that low a bar, it has no business being used in production imo.
-
Fuck yes, Italy!!National strike against Israel's genocide in Palestine.Fuck yes, Italy!!
National strike against Israel's genocide in Palestine. That's how it's done!! 🇵🇸