about
deadbyte / dbyte
i build dbyte because i want to understand the whole machine compiler VM native backend object files all within reach
what runs
13.5.0 is the latest locally sealed software release for Windows x64 and GNU/Linux x86-64. It adds bounded compile-time loops and pure compile-time functions. The historical 13.2.0 Linux release has the BIOSTAR physical-host qualification; 13.5.0 does not. DByte REAL_STORAGE remains DISARMED and FULL_OS is not claimed.
the rules
- One semantic authority. Backends do not invent language behavior.
- Raw source, package bytes and release identities outrank polished prose.
- Target-specific ABI and hardware facts stay target-specific.
- Virtual proof and physical proof are never merged by wording.
- Restore to known-good is a feature.
- Cut the problem boundary before adding another framework.
why own the stack
Libraries are fine when I can see the boundary. DBYTE owns the parts where owning them makes bugs easier to see or the output easier to reproduce. Rewriting the universe for fun would be stupid; the code budget is real.
If the prose and the machine disagree, the prose does not win because it looks nicer.
write code know the bytes
I am sick of software that needs a tower of tools just to print one line. A compiler ought to be something I can open, trace and fix. Source goes in. Instructions come out. If I cannot explain the middle, that is my problem to solve, not something to bury under another abstraction.
I do not want DBYTE to win a buzzword contest. I want the machine to do exactly what I told it to do. Smaller systems, hard evidence, and the freedom to pull the whole thing apart when it breaks. Terry A. Davis reminded me how far one stubborn programmer can take that idea. DBYTE is my own attempt, not a copy of his code.
license
For the upcoming 13.6.0 development branch, the original DBYTE code I own is dedicated to the public domain through CC0-1.0. Use it, study it, fork it, sell what you build with it. I am writing this compiler to make things, not to count how many times someone asks me for permission.
Release boundary: 13.6.0 is still a draft, not a download or a sealed release. The currently distributed 13.5.0 and earlier archives keep the license shipped inside each archive; their notices do not change retroactively. Dependencies, outside code and assets still belong to their own authors. See the actual release state.
two domains one site
i finally got dbytelang.org. Took long enough. I said I would get .org when I could afford it. Well, here it is. .org fits a non-profit hobby systems project better than .site. DBYTE is still not a company and I am still not building a subscription machine.
dbytelang.site is staying. Both domains run from the same Cloudflare Pages project. No second website to sync, no forced redirect and no extra hosting stack. I wanted another domain, not another machine to babysit.
in memory
Terry A. Davis (1969 - 2018). Rest in peace.
Thank you for what you gave us. Your work still reminds us that one person can build and understand a whole system.