Announcing remote system call support on bare metal
In this technical retrospective (2014), @lelf 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 Cloud & Mobile Era (2014–2019)
COMMUNITY SCORE ★ 28 points
TOTAL DISCUSSIONS 2 comments
very interessting stuff and I hope it takes off as the driver problem is keeping people away from running a different kernel - and you can even decide whether to run in kernel mode or not. imagine what else would then be possible with so much code reuse :) also they make a point with safety and ease of development (testing in userspace, valgrind)
Title should probably mention that this is about rump kernels for NetBSD/xen.