Earlier quoted context omitted.
Surely you mean 6fps
He doesn't: https://x.com/trq212/status/2014051501786931427
Claude Code daily benchmarks for degradation tracking
281–290 of 372 posts
Re: Claude Code daily benchmarks for degradation tracking
#282Earlier quoted context omitted.
Surely you mean 6fps
He doesn't: https://x.com/trq212/status/2014051501786931427
I'm just flabbergasted.
Re: Claude Code daily benchmarks for degradation tracking
#283Earlier quoted context omitted.
Surely you mean 6fps
He doesn't: https://x.com/trq212/status/2014051501786931427
Most people's mental model of Claude Code is that "it's just a TUI" but it should really be closer to "a small game engine".
For each frame our pipeline constructs a scene graph with React then
-> layouts elements
-> rasterizes them to a 2d screen
-> diffs that against the previous screen
-> finally uses the diff to generate ANSI sequences to draw
We have a ~16ms frame budget so we have roughly ~5ms to go from the React scene graph to ANSI written.Re: Claude Code daily benchmarks for degradation tracking
#284Hi everyone, Thariq from the Claude Code team here. Thanks for reporting this. We fixed a Claude Code harness issue that was introduced on 1/26. This was rolled back on 1/28 as soon as we found it. Run `claude update` to make sure you're on the latest version.
Anywhere we can read more about what a "harness issue" means? What was the impact of it?
In other words, it was the Claude Code _app_ that was busted
Re: Claude Code daily benchmarks for degradation tracking
#285Re: Claude Code daily benchmarks for degradation tracking
#286Earlier quoted context omitted.
He doesn't: https://x.com/trq212/status/2014051501786931427
For those who don't want to visit X: Most people's mental model of Claude Code is that "it's just a TUI" but it should really be closer to "a small game engine". For each frame our pipeline constructs a scene graph with React then -> layouts elements -> rasterizes them to a 2d screen -> diffs that against the previous screen -> finally uses the diff to generate ANSI sequences to draw We have a ~16ms frame budget so w…
Re: Claude Code daily benchmarks for degradation tracking
#287Earlier quoted context omitted.
He doesn't: https://x.com/trq212/status/2014051501786931427
What? Technology has stopped making sense to me. Drawing a UI with React and rasterizing it to ANSI? Are we competing to see what the least appropriate use of React is? Are they really using React to draw a few boxes of text on screen? I'm just flabbergasted.
Re: Claude Code daily benchmarks for degradation tracking
#288Hi everyone, Thariq from the Claude Code team here. Thanks for reporting this. We fixed a Claude Code harness issue that was introduced on 1/26. This was rolled back on 1/28 as soon as we found it. Run `claude update` to make sure you're on the latest version.
Is there compensation for the tokens because Claude wasted all of them?
Re: Claude Code daily benchmarks for degradation tracking
#289Earlier quoted context omitted.
He doesn't: https://x.com/trq212/status/2014051501786931427
For those who don't want to visit X: Most people's mental model of Claude Code is that "it's just a TUI" but it should really be closer to "a small game engine". For each frame our pipeline constructs a scene graph with React then -> layouts elements -> rasterizes them to a 2d screen -> diffs that against the previous screen -> finally uses the diff to generate ANSI sequences to draw We have a ~16ms frame budget so w…
Re: Claude Code daily benchmarks for degradation tracking
#290Earlier quoted context omitted.
He doesn't: https://x.com/trq212/status/2014051501786931427
For those who don't want to visit X: Most people's mental model of Claude Code is that "it's just a TUI" but it should really be closer to "a small game engine". For each frame our pipeline constructs a scene graph with React then -> layouts elements -> rasterizes them to a 2d screen -> diffs that against the previous screen -> finally uses the diff to generate ANSI sequences to draw We have a ~16ms frame budget so w…