matt_oriordan
Joined 14 years ago
Karma
196
Submissions
133
Member since
Nov 9
Joined 14 years ago
It's pong where the ball moves one step per model decision.
Four lanes, one model each, same serve, same rules.
Every step the model gets the same tiny JSON state (ball, paddle, predicted intercept) and the same question: up, down or stay. One answer moves the ball one segment; eight segments cross the court. No speed up / adjustments for real play, so a lane's speed is that model's decision latency.
Numbers, recorded on Vercel (iad1) next to the gateway, 45 seconds per lane: Jev averaged 227 ms (p95 400 ms). Gemini 3.2 s, Haiku 2.5 s, GPT-5.6 Sol 3.5 s.
In the first 12 seconds: 47 decisions vs 3, 2 and 2.
Bit of fun! Enjoy
Two weeks ago I built Jev Pong and thought it was.
Then I tried to find a use our customers would ship and couldn't, so I sorted the whole first week of Jev posts instead of guessing. The data is on a separate page linked from the piece (see https://mattheworiordan.github.io/jev-landscape/ and https://github.com/mattheworiordan/jev-landscape/, which scanned ~6k posts and looked at the data from two public gateways and twenty rapidly emerging rivals).
The short version. Adoption is very real (a quarter of Vercel's AI Gateway requests, 2% of its tokens), but the 100x claim is against frontier models. In practie, Jev is more like 7x and 5x against small models you'd have likely used.
So my conclusion is Jev is a great model, unblocks things you could not do before when you're in builder mode, but when you move into production and definitely do things at scale, you're unlikely to be on Jev. We have solutions already for the things Jev does, just with some friction.