miniblog.

← Back to all posts
Jan 15, 2023 at 10:22
Is Forth really a memory-unsafe language? I'm struggling to picture what e.g. a use-after-free would look like in such a minimal programming language.

Related Posts

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.
Mar 5, 2026 at 10:49
41
I'm still not sure whether a language should include a "kitchen sink linter" like Rust's clippy or have a package oriented "thousand flowers bloom" linter like eslint for JS and TS. Clippy is delightful out of the box but eslint makes it so easy to have project specific lints.