docs(twitter): add 2079746130309415185 corpus (NOTimothyLottes micro macro-forth rough-draft)

5-post design walkthrough of a branch-free 8-bit/word color-forth variant
for code generation: ~62 dict entries/page with paging, call/return
inlined by the compiler, branch-free compile + branch-free execution,
lookup-table pre-compile writes unaligned 8-bytes. Intended for tiny
self-contained chunks that include their own codegen. Whitney-esk in
single-char vars, non-Whitney in no higher-order arrays.
This commit is contained in:
ed
2026-07-26 21:33:59 -04:00
parent 41be106888
commit d2ee4f0ea0
3 changed files with 134 additions and 0 deletions
@@ -0,0 +1,46 @@
---
title: "A language that you author in a compressed space directly. So Whitney-esk in usi"
author: "NOTimothyLottes"
handle: "@NOTimothyLottes"
post_url: "https://x.com/NOTimothyLottes/status/2079746130309415185"
post_id: "2079746130309415185"
timestamp: "2026-07-22 01:51:31"
post_count: 5
reply_count: 0
repost_count: 0
like_count: 2
view_count: 318
---
# @NOTimothyLottes — A language that you author in a compressed space directly. So Whitney-esk in usi
## Post 1 (2026-07-22 01:35:49)
Working through rough draft of assembly for a different idea for a micro macro-forth.
1. 8-bit/word (color to relay meaning)
2. Roughly 62 useful dictionary entries/page
3. Supports paging (to extend dictionary)
4. Supports call/return - but compiler inlines everything
...
![Media 1](./media/2079742177370841105_1.png)
## Post 2 (2026-07-22 01:40:23) — reply to Post 1
5. Compile step is branch-free
6. Compiles to branch-free x86-64 source
7. Which is then executed
Noticed that I can pre-compile all the dictionary words into a lookup table. So actual compile just writes unaligned 8-bytes but only advances the write pointer by the actual size
## Post 3 (2026-07-22 01:43:56) — reply to Post 2
The interesting bits about this micro project was factoring out all branches, using branch-free interpreter loop to inline all calls so later execution is linear. Got messy doing a branch free software return stack. But costs are relatively low (40 ops/character)
## Post 4 (2026-07-22 01:46:15) — reply to Post 3
Intended usage would be for tiny-gramming programs in self contained chunks that include their own code generation (effectively a macro-forth used to generate machine code).
## Post 5 (2026-07-22 01:51:31) — reply to Post 4
A language that you author in a compressed space directly. So Whitney-esk in using lots of single character variables (or double character with page characters) -BUT- very non-Whitney in that it has no higher order array constructs