HackerTrans
トップ新着トレンドコメント過去質問紹介求人

csressel

no profile record

投稿

About the growing verification debt in software

clifford.ressel.fyi
4 ポイント·投稿者 csressel·4 か月前·0 コメント

How could Claude Code ever justify "a small game engine" (technical deepdive)

clifford.ressel.fyi
7 ポイント·投稿者 csressel·6 か月前·4 コメント

Show HN: Nori CLI, a better interface for Claude Code (no flicker)

github.com
37 ポイント·投稿者 csressel·6 か月前·9 コメント

コメント

csressel
·6 か月前·議論
That tokens per second you're describing is the token bandwidth to and from the API provider of the model, and that particular throughput doesn't cause the UI flicker. It likely only affects the interactive portion within the UI at the very bottom. Since most of the actual context tokens aren't shown (thinking tokens, structured json for tool calls or outputs, etc), it's likely much less than 60 FPS

The problem here was that before the December update, any time contents in the transcript history would change, they would include the entire history as part of the render loop, and completely clear and then completely reprint it on ever frame tick. For one brief rewrap of history, it's just a quick stutter, but when anything offscreen was changing for multiple seconds at a time, this created a constant strobe effect. Not a good look! https://github.com/anthropics/claude-code/issues/1913

This diagram explains the nature of the new vs old architecture a bit more visually https://x.com/trq212/status/2001439021398974720
csressel
·6 か月前·議論
yeah Friday on Xitter was a pretty disproportionate response imo!
csressel
·6 か月前·議論
first post was great, this should be interesting!
csressel
·6 か月前·議論
great feedback, thank you!
csressel
·6 か月前·議論
you got it right The main limitation versus Claude Code itself is just the exact feature parity. There are a lot of features at this point packed into CC, that it will take a little bit of time to get to exact feature parity. For example session resumes will be pretty easy to add, but session rewind and branching is a bigger ask
csressel
·6 か月前·議論
our vision with Nori CLI is to smooth the headache of hooking in skills and other customizations into any agent that's running under the hood, which I think is exactly in line with that. I see that Toad is also built on top of the ACP approach, so there's definitely an overlap or possible integration
csressel
·6 か月前·議論
good callout, I've seen Will McGugan's work on textual and rich before and that really pushed forward the Python+terminal ecosystem in the past five years. I've seen a lot of CLI tools coalesce on the rust and go ecosystems, for various reasons (uv, fzf, helix, just, etc). But I didn't know toad had gone open source now, very excited to check it out!