←back to thread

Grok Code Fast 1

(x.ai)
504 points Terretta | 1 comments | 29 Aug 25 13:01 UTC | HN request time: 0.204s | source
Show context
boole1854 ◴[29 Aug 25 14:21 UTC] No.45064512[source]▶
It's interesting that the benchmark they are choosing to emphasize (in the one chart they show and even in the "fast" name of the model) is token output speed.

I would have thought it uncontroversial view among software engineers that token quality is much important than token output speed.

replies(14): >>45064582 #>>45064587 #>>45064594 #>>45064616 #>>45064622 #>>45064630 #>>45064757 #>>45064772 #>>45064950 #>>45065131 #>>45065280 #>>45065539 #>>45067136 #>>45077061 #
jml78 ◴[29 Aug 25 14:30 UTC] No.45064630[source]▶
To a point. If gpt5 takes 3 minutes to output and qwen3 does it in 10 seconds and the agent can iterate 5 times to finish before gpt5, why do I care if gpt5 one shot it and qwen took 5 iterations
replies(2): >>45065130 #>>45074590 #
wahnfrieden ◴[29 Aug 25 15:07 UTC] No.45065130[source]▶
It doesn’t though. Fast but dumb models don’t progressively get better with more iterations.
replies(2): >>45065701 #>>45067855 #
1. dmix ◴[29 Aug 25 15:53 UTC] No.45065701[source]▶
That very much depends on the usecase

Different models for different things.

Not everyone is solving complicated things every time they hit cmd-k in Cursor or use autocomplete, and they can easily switch to a different model when working harder stuff out via longer form chat.