~/blog/2026-09-19/ $ cat post.md

orbitalis-3d is slowing down, on purpose

the student year started. here is where the hours are going instead, and why Orbitalis-3D is the thing that gives.

short one. the DAM course started this month, and between classes, the commute, and actually studying instead of skimming, the hours I had for a personal n-body simulator on evenings and weekends just got a lot smaller.

Orbitalis-3D is not cancelled. 0.4.0 (Barnes-Hut) is still the plan, and the roadmap in the repo has not changed. it just moves to whenever there is a free weekend instead of a predictable cadence, and I would rather say that plainly now than post nothing for two months and let people guess why.

what does not slow down

open source contributions and tinyOS keep going at the same pace as before. that is a deliberate ordering, not a default.

a kernel patch or a tinyOS commit is small, self-contained, and finishes in one sitting. a real review from a maintainer teaches me things a solo project cannot, because nobody is checking my n-body maths for a race condition I did not think to test. and the SerenityOS patch I just got merged is the clearest evidence I have that this is the work actually worth the limited hours right now.

Orbitalis-3D is a bigger, slower kind of project by design, six-step milestones, long write-ups, measuring everything twice. that is exactly the shape of project that survives being picked up again after a gap. it does not need me every week. the smaller stuff benefits more from staying consistent, so that is where consistency goes.

what to expect here

fewer Orbitalis-3D posts, whenever a milestone actually lands rather than on a schedule. more of the smaller kernel and tinyOS entries in between, since those keep happening regardless.

0.4.0 will get the same write-up treatment as 0.1.0 through 0.3.0 when it is done. it is just going to take longer to get there this semester than it would have over the summer.

← Back to blog