miniblog.

Futhark's design is deliberately trying to stay simple to keep long term design sustainable. The author also has an interesting discussion of relative versus absolute paths in import syntax, and how relative paths can make local analysis easier.

On thinking of books like software, treating them as evolving artifacts, and URLs versus paper book publishers:

Displaying value information in an IDE is tricky. For union types, it's more helpful to see the inferred type (Option<Player> versus null). For product types it's often nicer to see an example value. For primitive types I almost always want a value (0 versus int).