miniblog.

← Back to all posts
May 6, 2016 at 21:20
Smalltalk has separate True and False classes. Strictly following 'everything is OO', it makes sense: eg different 'not' implementations!

Related Posts

Sep 22, 2024 at 01:37
JSON is too small (no comments) and YAML is too big (many string syntaxes, relatively few implementations). TOML is in the sweet spot for complexity, but I agree this syntax is by far the most confusing part. TOML 1.1 improves it at least:
Proposal: Allow newlines and trailing commas in inline tables · Issue #516 · toml-lang/toml
Proposal: Allow newlines and trailing commas in inline tables · Issue #516 · toml-lang/toml
Overall I really like toml and its syntax feels very obvious to me for the most part. The only thing that doesn't is the expclicit cripling of inline tables, i.e. inline tables cannot have newlines...
Dec 12, 2023 at 00:55
What software designs require clean slate 'revolution' implementations, rather than evolution? I can think of: borrow checking in a PL (existing code is unsafe), microkernels (architecture is too different from monokernels), and full REPLs (can't add type redefinition later).
Oct 11, 2022 at 05:19
@friend It seems like people find Zig comptime easier to reason about, hence the interest in introducing it to other languages. That seems worth something. I still prefer Lisp/Clojure style macros over safer Scheme/Rust macros. Lisp macro implementations are closer to typical code.