anton.kundenko
← writing

initial commit

summary: the rayforce repo went on disk today. seven files, a hundred and three lines, no allocator, no test.

RayforceDB Rayforce: restart in C for embeddability work: Feb 2023 milestone
· 1 min read · #rayforce#c

Core idea: the first Rayforce commit is useful because of what it excludes: dependencies, framework assumptions, and public API commitments made before the engine shape was known.

The interesting thing about today's initial commit is what is not in it.

.gitignore     3
LICENCE        0
README.md      0
src/Makefile  17
src/main.c    42
src/storm.c    1
src/storm.h   40

Seven files, one hundred and three lines. There is no vendor/ directory. There is no third_party/. There is no logging library. There is no error-handling framework. There is no language, no parser, no REPL, no allocator, no test. None of those things land today.

The most expensive code in any project is the code you did not write. The library you take is forever yours to debug, regardless of who wrote it. Every absence in this commit is a future debt I have refused to take on. I will pay each of them in code, later, when I know what shape they should have. Today I want the absences logged.