はてなブックマーク

In a recent podcast about Rust leadership, the BDFL question came up again and Jeremy Soller said (in the understatement of the century) that "I believe Graydon would have said no to some things we all like now". And this echoes a different conversation on reddit where I was reminded that I meant to write down at some point how "I would have done it all differently" (and that this would probably h

This is a blog post (as solicited) about my suggestions for the Rust project in 2019 and beyond. I should note that I am speaking only for myself, not anyone else, and not even as a very active participant in Rust anymore. Moreover these suggestions, to a large extent, apply to many projects. Rust is just one case, but one that is currently doing some conscious year-end reflection. I should also n

Warning: this has turned out to be a .. long post. Recently, on the twitters, Stephanie Hurlburt suggested that it'd be healthy for people who have been around the computering industry for a while (*cough cough*) to take some "audience questions" from strangers. I obliged, and someone asked me an interesting one: "After memory safety, what do you think is the next big step for compiled languages t

Well-known things I'm very proud that rust shipped 1.0 without: null pointers array overruns data races wild pointers uninitialized, yet addressable memory unions that allow access to the wrong field Less-well-known things I'm very proud that rust shipped 1.0 without: a shared root namespace variables with runtime "before main" static initialization (the .ctors section) a compilation model that re

I don't often give talks about Rust, but I was in Tokyo recently during the Rust 1.0 release and figured I'd drop in on the Mozilla Tokyo office release party. I figured they'd try to make me talk about something, so I prepared a lightning talk. As is typical of my Rust-project communication style, I presented in point form. This is the contents of the talk: Five lists of six things about Rust: Si

Today Apple introduced a new language called Swift, along with some pretty hot livecoding environment which, while neat, is an area I'm not very expert in so I'm going to ignore. I am certain the livecoding nerds will discuss it elsewhere. Swift-the-language I've just finished (quickly and lightly) reading the manual for, so I'll suggest you take my commentary with a grain of salt, but I can point