imo, an ideal online textbook would be comprised of 3 components 📖:
1. git - version control, fork-ability🍴
2. wikipedia - editing (with markdown and LaTeX), open collaboration 👨💻
3. jupyter - compute-ability / interact-ability (with python 🐍)
[1] any live body of knowledge💡
@geoffreylitt@anselm_io opus as fast generator / coder; codex as slow discriminator / reviewer
they’re just tools on a speed-intelligence spectrum; people should learn to use the entire range
@thdxr it is easier to sync and build local first apps with SQLite than jsonl.. I actually think more chat apps should local first like linear, coding and cowork harnesses included.. terminal, docs, spreadsheets, they were all local first ages ago.
@hudzah You can probably associate the tool call id with each hunk, and switch between file view and chat view. In file view, show associated messages as “comments”.
depends on what you're doing: for web development, iteration speed matters more so typescript/JIT is preferred at the cost of run-time safety (correctness here is more subjective + about the pixels).
for backend development, safety matters more so compilation time is worth the cost.
hopefully, programming languages and test-time compute can be co-designed, and perhaps we get a single language + model that does all.