Loko Scheme: bare metal optimizing Scheme compiler
In this technical retrospective (2025), @dTal shares practical architectural lessons learned from running, scaling, or migrating production software under lean constraints.
Core Principles for Independent Builders:
Defaulting to simpler architectures (such as monolithic frameworks, SQLite, or managed VPS) prevents early engineering bankruptcy.
Evaluating true compute and egress costs reveals that high cloud bills can often be slashed by 80%+ through judicious re-platforming.
Code you write at 2 AM as a solo engineer must be easy to debug six months later without complex microservice dependencies.
Community Debate Themes:
HN engineers debated the tradeoffs between cloud convenience and raw server economics, database indexing strategies, and resisting premature architectural complexity.
CATEGORY Frugal Engineering →
HISTORICAL ERA Post-ZIRP & AI (2023–2026)
COMMUNITY SCORE 165 points
TOTAL DISCUSSIONS 15 comments
That one could be a big deal.
https://scheme.fail/manual/loko.html#Concurrency ↗
The docs don't mention channels and say that fibres are built on limited continuations (call/cc) which suggests missing some of the clever stuff in CML (e.g. that threads deadlocked on a channel get garbage collected)
This looks nice and very interesting that this runs on bare metal. Is more documentation / tutorials available anywhere?
EDIT: Found the documentation: https://scheme.fail/manual/loko.html ↗
I also like that it runs on bare metal. I wonder is it builds and runs on macOS? (I am on a mobile device and can’t check it myself.)
Off topic, but I love the design of the linked web site.
This is super interesting. I kind of want to use this to turn one of my old laptops into a Scheme machine. But from the docs I think on bare metal it's only usable over serial.
Nice achievement, building on the foregone dreams of Lisp powered workstations.
We need more efforts like these and less yet another UNIX clone in C.