miniblog.

← Back to all posts
Dec 24, 2022 at 05:43
I suspect every programming language eventually becomes dated. As soon as you commit to 1.0, you will have design decisions that (with hindsight) are mistakes, and you can't fix them. Design best practices change over time too. Immutability is a more common default now.

Related Posts

May 27, 2026 at 21:28
25
I'm writing a Path type in my programming language but not sure what methods belong on a Path. Should I have some_path.read_string() or fs::read_string(some_path) instead? I love .method() for IDE completion, but I don't want Path to be cluttered. I'm also trying to avoid UFCS.
Mar 29, 2026 at 13:54
1
The author of rust-analyzer discussing how language features help or hinder fast IDEs. If you allow `from m import *` you can't analyse files in isolation, and it's even harder in Rust.
Against Query Based Compilers
Query based compilers are all the rage these days, so it feels only appropriate to chart some treacherous shoals in those waters.
Mar 20, 2026 at 12:02
223
Excellent series on Self, both the programming model and the tool chain. I love how opening an inspector on a value (e.g. nil) then shows a link to all occurrences of the value in other open inspectors!
Environment and the programming language Self (part one; environment)
Environment and the programming language Self (part one; environment)
I bring you a message about a language that has been at the birth of many others, but almost no one knows it. A rumor of a graphical environment offering options like no other, but almost no one using it. I also bring information about a virtual machine supporting reflection almost to infinity, reaching almost half of the operating power of C in numerical calculations in its time, yet today forgotten.