Loading video...

Video Failed to Load

Go Home

Opus 4.6 vs Gemini Pro 3.1 (7/9) I wanted to do a physics simulation test, overall both models did a good job in this department, however Opus added nice animations to things like "Fan", "Magnet" whilst gemini just rendered them out as a red circle. Opus also included way...

28,179 views • 7 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

GEMINI 3 LAUNCH IS HERE I got a SNEAK PEEK at Gemini 3 with Logan Kilpatrick (Google Deepmind), and it might be the most POWERFUL vibe-coding tool on the planet. A little breakdown: 1. Anyone can build 3D and casual games now You can vibecode full, playable 3D video games generated in minutes. Actual games with physics, characters, controls, and loops you can remix instantly. Pure insanity. I can see founders and brands spinning up games on the fly to ride trends and drive growth. 2. Intelligent apps are becoming the default We built apps where reasoning, memory, and multi-step planning were baked in from the start. Once you’re building apps with ACTUAL intelligence baked in, there’s a whole wave of new opportunities that weren’t possible before. 3. Gemini acts like a creative partner You describe the idea, Gemini fills in the gaps, challenges decisions, proposes alternatives, and iterates in real time. 4. Vibe coding hits a new level Gemini 3 can generate assets, code, game logic, UI, and narrative in one flow. Tools like Claude and Cursor feel fast. This feels like the next layer, the one where a single builder can compete with full teams. Logan Kilpatrick and I pushed Google Gemini 3 hard, and the outputs were solid. A few times we had to give it a few extra prompts but it took feedback really well. I think 1 year ago, a lot of people discounted Google in the AI arms race. Can you discount them anymore? Doubt it. After this, it feels like they at best leading, at worst leading. What do you think of Google's AI efforts/Gemini 3 My biggest takeaway was how it just felt like Gemini 3 had a little more vibe coding horsepower than anything I’ve used.

GREG ISENBERG

73,886 views • 10 months ago

I just compared Claude Code vs Codex vs Cursor CLI The task was to build a Next.js app with Tailwind 4 and shadcn components to collect customer feedback and showcase it with a widget. I gave all three the same prompt and let them go for 30 minutes to see what they came up with. Claude Code with Opus 4.1 Even though I told it to set up the app in the existing project folder, it tried to create a directory for it. After I interrupted and told it not to do that, it built a demo form and landing page with no errors. I had to ask it to make the demo interactive so users could submit a testimonial and preview it. The landing page looked like AI and was pretty basic, but it worked and it was done in a fraction of the time of the others. Total tokens used: 33k Codex with GPT-5 At the end of the 30 minutes I just could not get Codex to produce a working app. It got stuck in a loop of not being able to set up Tailwind 4 and despite many, MANY, attempts, I ended up with a "failed to compile" error. Total tokens used: 102k Cursor Agent with GPT-5 This was the slowest agent by far and a couple of times I actually thought it got stuck in a loop and was close to Ctrl+C'ing to cancel it. The TUI is really nice though, especially how it shows diffs and it did eventually build a working app (after one or two slight errors that needed fixing) The demo was interactive and it had a very minimal design that looked bare but also a lot less like an "AI generated" app than the Opus 4.1 design. It also wasn't too chatty and just did what it needed to do! Code quality was on a par with Opus 4.1, but it did use 5.5x as many tokens to get there. Still cheaper than Opus on a direct comparison but not when you factor in a Claude Code Max subscription. Total tokens: 188k I'll be able to do a proper comparison and record some videos when I'm back from holiday but for now, Opus is still the more capable model out of the box and Claude Code is the more complete CLI product. It will be interesting to see how Cursor evolve their CLI though with commands and subagents because I think with GPT-5 they have a real shot at providing competition for Claude Code if they can optimise output to get similar quality with less tokens. Jump to 0:40 in the video to see the two apps. Which do you think is which? ;)

Ian Nuttall

195,173 views • 1 year ago

sonnet 5 vs sonnet 4.6 vs opus 4.8 vs glm 5.2 – frontend tasks dropped sonnet 5 into a quick test today. same three prompts to all four models, single-shot html/canvas, no edits: • objects falling on a trampoline • rockets playing tennis • a slingshot breaking bottles ranked by speed (total across the 3 tasks): 1. opus 4.8 – 15m 09s 2. sonnet 5 – 16m 05s 3. glm 5.2 – 27m 18s 4. sonnet 4.6 – 35m 06s ranked by code shortness (total loc): 1. sonnet 5 – 1794 2. opus 4.8 – 2063 3. sonnet 4.6 – 2182 4. glm 5.2 – 3285 sonnet 5 came out on top here – leanest code overall and a near-tie for fastest it was also the most creative. in every task it added something none of the others did: – kept the trampoline vibrating after the objects landed – drew a +1 next to the rocket that scored the point – turned the slingshot to face the next bottle before each shot opus 4.8 evaluated the code sonnet 5 produced. four things stood out: • the sphere is a fake, and that's the smart move. the cube and star are real 3d meshes with proper culling and shading, but the ball is just a flat shaded circle. a lit sphere looks identical from every angle, so building it in 3d would burn compute for zero visible payoff. knowing where not to bother is its own kind of skill • weight actually means something on the trampoline. the star is heavy, so it barely bounces and dents the mat hard. the ball is light, so it's lively and leaves a shallow dip. the three objects aren't just different shapes – they have different temperaments, and the physics is what gives them that • the slingshot is framed like a shot, not just drawn. the handle is anchored below the bottom of the screen and runs off-frame, so it reads as something you're holding rather than a sprite parked in the scene. that's a staging instinct, not a rendering one • the paddle ai forward-simulates the ball to predict where it'll land, then adds a deliberate error bias (roughly 1 in 5 shots is a real miss). that's why scoring looks natural instead of robotic – plus four distinct fault types with a catch-all so a rally never hangs without a result bottom line: sonnet 5 does more with less. fastest tier, leanest code, and the only one that added small touches nobody asked for follow thehype. for 24/7 ai news, analysis and breakdowns

thehype.

14,518 views • 3 months ago