git » homepage.git » commit 8c85e4e

Refine Forth-to-grid linkage

author Alan Dipert
2026-02-21 03:04:48 UTC
committer Alan Dipert
2026-02-21 03:04:48 UTC
parent f4fb466715689b94f532124baeadcec38ac2aced

Refine Forth-to-grid linkage

md/_GridCalc.md +2 -2

diff --git a/md/_GridCalc.md b/md/_GridCalc.md
index 115da57..4ceb1bb 100644
--- a/md/_GridCalc.md
+++ b/md/_GridCalc.md
@@ -20,9 +20,9 @@ What follows is a retrospective on how that happened, why it looks the way it do
 
 I learned [Forth](https://en.wikipedia.org/wiki/Forth_(programming_language)) around 2011, and what stuck with me was not just the stack but the flatness of the syntax: words, space-separated, linear, no parentheses, no precedence, a stream of tokens in plain sight.
 
-It felt like a language that wanted to be handled like physical tokens, where you drag words around, reorder them, insert one between two others, and treat the code as something you can literally move with your hands. I never prototyped that idea, but it never went away.
+It felt like a language that wanted to be handled like physical tokens, where you drag words around, reorder them, insert one between two others, and treat the code as something you can literally move with your hands.
 
-The implication of that kind of free drag-and-drop editing is that you can accidentally land in a structurally invalid program. The grid sketch was my answer: a constrained layout that only lets you build valid programs.
+An implication of that kind of free drag-and-drop editing is that you can accidentally land in a structurally invalid program. On mobile I was dissatisfied with open editing, because it seemed like you want constrained, structural editing. The grid sketch was my answer: a constrained layout that only lets you build valid programs. I never prototyped that idea, but it never went away.
 
 ## The notebook sketch