-
Notifications
You must be signed in to change notification settings - Fork 0
Rewrites #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: book
Are you sure you want to change the base?
Rewrites #6
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -108,3 +108,4 @@ Thumbs.db | |
| ehthumbs.db | ||
| Desktop.ini | ||
|
|
||
| .obsidian/ | ||
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
| @@ -1,3 +1,5 @@ | ||||||||
| SHELL := /bin/bash | ||||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🧹 Nitpick | 🔵 Trivial Hardcoding bash is fine, but document why. You're forcing +# Bash required for progress target (uses arrays and (( )) arithmetic)
SHELL := /bin/bash📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||
|
|
||||||||
| TEX_MAIN := tex/computer.tex | ||||||||
| BUILD_DIR := build | ||||||||
| OUT_PDF := computer.pdf | ||||||||
|
|
@@ -6,6 +8,7 @@ SVG_SRCS := $(wildcard svg/*.svg) | |||||||
| SVG_PDFS := $(SVG_SRCS:.svg=.pdf) | ||||||||
|
|
||||||||
| .PHONY: all clean | ||||||||
| .PHONY: progress | ||||||||
|
|
||||||||
| all: $(OUT_PDF) | ||||||||
|
|
||||||||
|
|
@@ -35,3 +38,24 @@ clean: | |||||||
| latexmk -C -output-directory=$(BUILD_DIR) $(TEX_MAIN) || true | ||||||||
| rm -rf $(BUILD_DIR) $(OUT_PDF) | ||||||||
| rm -f tex/computer.{aux,log,out,fls,fdb_latexmk,synctex.gz,pdf} | ||||||||
|
|
||||||||
| progress: | ||||||||
| @set -e; \ | ||||||||
| file="ROADMAP.md"; \ | ||||||||
| done=$$(grep -ao "✅" "$$file" | wc -l | tr -d " "); \ | ||||||||
| doing=$$(grep -ao "⏳" "$$file" | wc -l | tr -d " "); \ | ||||||||
| todo=$$(grep -ao "◽️" "$$file" | wc -l | tr -d " "); \ | ||||||||
| total=$$((done + doing + todo)); \ | ||||||||
| if [ $$total -eq 0 ]; then pct=0; else pct=$$(((100*done + total/2)/total)); fi; \ | ||||||||
| width=20; filled=$$(((pct*width + 50)/100)); \ | ||||||||
| bar_short="["; for ((i=1;i<=width;i++)); do if [ $$i -le $$filled ]; then bar_short="$$bar_short█"; else bar_short="$$bar_short░"; fi; done; bar_short="$$bar_short]"; \ | ||||||||
| width2=49; filled2=$$(((pct*width2 + 50)/100)); \ | ||||||||
| bar_long="["; for ((i=1;i<=width2;i++)); do if [ $$i -le $$filled2 ]; then bar_long="$$bar_long█"; else bar_long="$$bar_long░"; fi; done; bar_long="$$bar_long]"; \ | ||||||||
| bottom="0 10 20 30 40 50 60 70 80 90 100"; \ | ||||||||
| for f in ROADMAP.md README.md; do \ | ||||||||
| [ -f "$$f" ] || continue; \ | ||||||||
| PROGPCT="$${pct}% ($${done}/$${total})" perl -0777 -CS -Mutf8 -pi -e 'my $$r=$$ENV{PROGPCT}; s|<!-- PROGRESS_PCT(?:_README)? -->.*?<!-- /PROGRESS_PCT(?:_README)? -->|<!-- PROGRESS_PCT -->$$r<!-- /PROGRESS_PCT -->|sg' "$$f"; \ | ||||||||
| PROGBAR_SHORT="$${bar_short}" perl -0777 -CS -Mutf8 -pi -e 'my $$r=$$ENV{PROGBAR_SHORT}; s|<!-- PROGRESS_BAR(?:_README)? -->.*?<!-- /PROGRESS_BAR(?:_README)? -->|<!-- PROGRESS_BAR -->$$r<!-- /PROGRESS_BAR -->|sg' "$$f"; \ | ||||||||
| PROGBAR_LONG="$${bar_long}" BOTTOM="$${bottom}" perl -0777 -CS -Mutf8 -pi -e 'my ($$r,$$b)=@ENV{qw/PROGBAR_LONG BOTTOM/}; s|(<!-- progress -->\n```text\n)[^\n]*\n[^\n]*\n(```\n<!-- /progress -->)|$$1$$r\n$$b\n$$2|sg' "$$f"; \ | ||||||||
| done; \ | ||||||||
| echo "Updated progress to $${pct}% ($${done}/$${total}) across ROADMAP.md and README.md" | ||||||||
|
Comment on lines
+42
to
+61
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This target is a maintainability minefield. Several concerns with this progress tracking implementation:
Consider extracting this to a standalone script with proper error handling and comments: progress:
- @set -e; \
- file="ROADMAP.md"; \
- done=$$(grep -ao "✅" "$$file" | wc -l | tr -d " "); \
- ...
+ @./scripts/update-progress.shThen create
🧰 Tools🪛 checkmake (0.2.2)[warning] 42-42: Target body for "progress" exceeds allowed length of 5 (19). (maxbodylength) |
||||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -14,6 +14,20 @@ | |
| <p>By James Ross</p> | ||
| </div> | ||
|
|
||
| ## Status | ||
|
|
||
| **Overall Progress:** <!-- PROGRESS_PCT -->39% (178/460)<!-- /PROGRESS_PCT --> | ||
| <!-- PROGRESS_BAR -->��]<!-- /PROGRESS_BAR --> | ||
|
|
||
| [Roadmap & checklist →](ROADMAP.md) | ||
|
|
||
| <!-- progress --> | ||
| ```text | ||
| ��] | ||
| 0 10 20 30 40 50 60 70 80 90 100 | ||
| ``` | ||
| <!-- /progress --> | ||
|
Comment on lines
+17
to
+29
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Corrupted Unicode — progress bar is garbage. Lines 20 and 26 contain This renders as literal garbage in the README. Either:
-<!-- PROGRESS_BAR -->��]<!-- /PROGRESS_BAR -->
+<!-- PROGRESS_BAR -->[===============> ]<!-- /PROGRESS_BAR -->
<!-- progress -->
```text
-��]
+[===============> ]
0 10 20 30 40 50 60 70 80 90 100In README.md around lines 17 to 29 the progress bar contains corrupted Unicode |
||
|
|
||
| ## What if computation had a shape? | ||
|
|
||
| Not metaphorically. Not as a diagram on a whiteboard. But as a navigable geometry, where programs move through possibility space, bugs are wrong turns, optimizations are shorter paths, and every execution leaves a trail you can walk backward. | ||
|
|
||
Large diffs are not rendered by default.
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -10,7 +10,16 @@ \chapter*{Part I --- The Universe as Rewrite} | |||||||||||||||||||||||||||||||||||||
| \textbf{Computation is what reality is made of, not what we do \emph{to} reality.} | ||||||||||||||||||||||||||||||||||||||
| \end{quote} | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| Up to now, most of us have only seen the shadows of this truth—projected, flattened, and made safe by decades of comforting abstractions. This book asks you to turn toward the source, to see the forms behind the shadows. Everything that follows traces the geometry of that world. | ||||||||||||||||||||||||||||||||||||||
| Up to now, most of us have only interacted with computation through | ||||||||||||||||||||||||||||||||||||||
| \emph{abstractions}—interfaces designed to hide structure, flatten history, and | ||||||||||||||||||||||||||||||||||||||
| sanitize the underlying machinery. What we call “code” is often just the | ||||||||||||||||||||||||||||||||||||||
| silhouette of a far richer process. | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| This book asks you to look directly at that process: to stop reasoning from | ||||||||||||||||||||||||||||||||||||||
| interfaces and start reasoning from \emph{structure}. Once you do, a different | ||||||||||||||||||||||||||||||||||||||
| picture emerges—a picture with geometry, causality, and motion. Everything that | ||||||||||||||||||||||||||||||||||||||
| follows is an attempt to map that deeper layer with precision. | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
|
Comment on lines
+13
to
+22
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Straight quotes detected — typographic sin. Line 15 uses ASCII straight quotes: -sanitize the underlying machinery. What we call "code" is often just the
+sanitize the underlying machinery. What we call ``code'' is often just the📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| \subsection*{Why This Matters: From Black Boxes to Glass Boxes} | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
|
|
@@ -123,7 +132,7 @@ \subsection*{A Call to Action: Go Bend Some Universes} | |||||||||||||||||||||||||||||||||||||
| We have laid the foundation for a computational cosmology. You now hold the keys to a system that replaces probabilistic guesswork with deterministic geometry, and opaque processes with absolute provenance. This is not an evolution. It is an architectural revolution. | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| \begin{quote} | ||||||||||||||||||||||||||||||||||||||
| \textbf{Those who finish this book will not see computation the same way again. Once you learn to perceive the geometry beneath the code, the old mindset of “just running the code” collapses into a kind of flatness. It is like stepping outside Plato’s cave: the familiar shadows of computation give way to a full, three-dimensional world of structures, laws, and histories that were always there, waiting to be seen.} | ||||||||||||||||||||||||||||||||||||||
| \textbf{Those who finish this book will not see computation the same way again. Once you learn to perceive the geometry beneath the code, the old mindset of “just running the code” collapses into a kind of flatness. It is like switching from a diagnostic log to a full-system trace: the flat, fragmented view of computation you once relied on is replaced by a living, three-dimensional landscape of structures, laws, and histories that were always there—just never visible at once. Once you learn to see in this geometry, the old mindset of “just running the code” collapses into something impossibly thin.} | ||||||||||||||||||||||||||||||||||||||
| \end{quote} | ||||||||||||||||||||||||||||||||||||||
|
Comment on lines
+135
to
136
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Egregious repetition — did you paste twice? This single paragraph says essentially the same thing twice:
Same structure, same subject, same verb, same object. This reads like a merge conflict that was resolved by keeping both versions. Kill one. Additionally, -\textbf{Those who finish this book will not see computation the same way again. Once you learn to perceive the geometry beneath the code, the old mindset of "just running the code" collapses into a kind of flatness. It is like switching from a diagnostic log to a full-system trace: the flat, fragmented view of computation you once relied on is replaced by a living, three-dimensional landscape of structures, laws, and histories that were always there—just never visible at once. Once you learn to see in this geometry, the old mindset of "just running the code" collapses into something impossibly thin.}
+\textbf{Those who finish this book will not see computation the same way again. Once you learn to perceive the geometry beneath the code, the old mindset of ``just running the code'' collapses into a kind of flatness. It is like switching from a diagnostic log to a full-system trace: the flat, fragmented view of computation you once relied on is replaced by a living, three-dimensional landscape of structures, laws, and histories that were always there---just never visible at once.}📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| If you are a physicist, expect parts of this to feel like an API spec for the laws you already know. If you are a computer scientist, expect ``the machine'' to suddenly include galaxies. If you are an ML person, expect models to shrink back down to what they are: ways of steering flows through a much larger space. | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧹 Nitpick | 🔵 Trivial
Consider ignoring additional Obsidian artifacts beyond the vault directory.
Obsidian generates not only the
.obsidian/vault metadata directory, but also per-vault.obsidian.jsonfiles and workspace-specific configuration. Depending on your project philosophy (treat vault config as project state vs. ignore editor state), you may need:Verify whether
.obsidian.jsonshould be gitignored in this repository.🤖 Prompt for AI Agents
🛠️ Refactor suggestion | 🟠 Major
Misplaced entry: Relocate
.obsidian/to the dedicated editor section.This entry is positioned orphaned after the "Other generic editor/OS clutter" section. Given that Obsidian is a first-class editor/IDE, it belongs with the other structured editor entries (VS Code, JetBrains, Xcode, etc.) starting at line 79, complete with its own subsection comment. Grouping it at the tail end of the file dilutes the organizational coherence.
Restructure as follows—remove the orphaned entry and add it to the editor section:
🤖 Prompt for AI Agents