OpenAI: Trapped in 2nd place 🔗 **Source:** [OpenAI: Trapped in 2nd place](https://www.youtube.com/watch?v=_nxbZgZysT4) > [!note]+ Document Notes > tags: [ai-industry, openai, market-competition, chatgpt, ai-models] > author: Theo - t3․gg > source: YouTube > reference: https://www.youtube.com/watch?v=_nxbZgZysT4 > date created: 2025-01-25 13:30 > > # 🏷️ Title: OpenAI: Trapped in 2nd Place > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Evaluate OpenAI's strategy vs. competitors across programming use cases — 03:45 #programming - [H2] Monitor chat experience market share changes for competitive threats — 15:20 #strategy - [H3] Track document analysis capabilities gap between models — 25:10 #capabilities ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [OpenAI Models](https://platform.openai.com/docs/models) - [Anthropic Claude](https://www.anthropic.com/claude) ## 📝 Summary - OpenAI consistently ranks second across programming, image generation, document analysis, and tool calling despite releasing groundbreaking features first - Their primary competitive advantage remains the ChatGPT interface, which captures 70% of their revenue and maintains user retention - Google and Anthropic repeatedly surpass OpenAI's technical capabilities within months of major releases - OpenAI's strategy focuses on "good enough" performance across categories rather than excellence in any single domain - The company's survival depends on maintaining chat experience leadership rather than technical superiority ## 📖 Main Content OpenAI faces a recurring pattern where they introduce revolutionary AI capabilities only to be surpassed by competitors within months. Despite pioneering reasoning models with GPT-5, DeepSeek's R1 matched performance while offering open weights. Similarly, GPT Image dominated until Google's "Nano Banana" models exceeded capabilities at faster speeds. The analysis examines six key AI categories: programming, chat experience, image generation, document analysis, agent tool calling, and browser use. OpenAI ranks second or lower in five categories, with their only first-place position being chat experience through ChatGPT. This positioning reflects OpenAI's strategic focus on platform retention rather than technical dominance. With 70% of revenue from ChatGPT subscriptions, they prioritize maintaining user engagement over benchmark leadership. The approach succeeds because users prefer integrated "good enough" solutions over switching between specialized tools. However, this strategy carries risks. Google's distribution advantages and potential interface improvements could threaten OpenAI's chat dominance. The company's "Code Red" response to a 7% traffic decline demonstrates their sensitivity to user retention metrics. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/_nxbZgZysT4?t=0) — [H1] OpenAI's recurring competitive pattern - Key idea: OpenAI introduces paradigm-shifting features then gets surpassed by competitors - Evidence: "GPT-5 changed how models work entirely by introducing reasoning... DeepSeek drops R1 with similar numbers" #### ⏱️ [02:15](https://youtu.be/_nxbZgZysT4?t=135) — [H2] Market collapse from Chinese competition - Key idea: DeepSeek's open-weight model caused immediate market disruption - Evidence: "The whole market collapsed as a result" of free alternative with similar performance #### ⏱️ [03:45](https://youtu.be/_nxbZgZysT4?t=225) — [H1] Programming model rankings established - Key idea: Anthropic's Opus 4.5 currently leads programming tasks over GPT models - Evidence: "Opus is built different... it's my default now in cursor, shipping way more code" #### ⏱️ [06:30](https://youtu.be/_nxbZgZysT4?t=390) — [H2] CLI tool competition dynamics - Key idea: OpenAI's Codecs fell behind despite promising open-source start - Evidence: "Codecs has not meaningfully improved... Cloud Code has found its position pretty far ahead" #### ⏱️ [09:15](https://youtu.be/_nxbZgZysT4?t=555) — [H1] Chat experience as OpenAI's stronghold - Key idea: ChatGPT interface remains OpenAI's primary competitive advantage - Evidence: "70% of their revenue... when people refer to AI, they're often referring to ChatGPT" #### ⏱️ [12:20](https://youtu.be/_nxbZgZysT4?t=740) — [H2] Model conversation quality assessment - Key idea: GPT models produce unpleasant emoji-heavy responses compared to competitors - Evidence: "I am so tired of the emoji riddled slop that we get out of GPT" #### ⏱️ [15:45](https://youtu.be/_nxbZgZysT4?t=945) — [H1] Image generation leadership shift - Key idea: Google's Nano Banana models surpassed GPT Image in speed and capability - Evidence: "Nano Banana generates in seconds... no piss filter, roughly same accuracy" #### ⏱️ [19:30](https://youtu.be/_nxbZgZysT4?t=1170) — [H2] Nano Banana Pro's advanced capabilities - Key idea: Google's model generates complete slide decks with proper text integration - Evidence: "It can generate full slide decks... proper spatial awareness... almost scary" #### ⏱️ [22:10](https://youtu.be/_nxbZgZysT4?t=1330) — [H1] Document analysis dominance by Google - Key idea: Gemini models excel at large context document processing - Evidence: "Gemini is so far ahead... chews through PDFs, finds needles in haystacks really well" #### ⏱️ [25:15](https://youtu.be/_nxbZgZysT4?t=1515) — [H2] Tool calling reliability comparison - Key idea: Anthropic leads in reliable agent tool usage over OpenAI - Evidence: "Opus 4.5 closed whatever gaps... I don't get errors from Opus, occasionally get errors from GPT" #### ⏱️ [28:45](https://youtu.be/_nxbZgZysT4?t=1725) — [H1] Scoring system reveals OpenAI strategy - Key idea: Despite second-place rankings, OpenAI leads overall through consistent performance - Evidence: Point scoring shows OpenAI at 12 points vs competitors at 10-11 #### ⏱️ [31:20](https://youtu.be/_nxbZgZysT4?t=1880) — [H1] "Good enough" strategy explanation - Key idea: OpenAI prioritizes platform retention over technical excellence - Evidence: "They don't have to be as good as Opus... if they're 5% worse but you're already paying, who cares?" #### ⏱️ [34:15](https://youtu.be/_nxbZgZysT4?t=2055) — [H2] Revenue model dependency on chat experience - Key idea: ChatGPT subscriptions drive 70% of revenue, making chat experience critical - Evidence: "Code Red happened because they saw 7% dip in week-over-week traffic" #### ⏱️ [36:50](https://youtu.be/_nxbZgZysT4?t=2210) — [H1] Google's distribution advantage threat - Key idea: Google's app ecosystem could threaten OpenAI if properly integrated - Evidence: "Google has insane distribution... if they integrate AI properly, incentive to use ChatGPT goes down" #### ⏱️ [38:30](https://youtu.be/_nxbZgZysT4?t=2310) — [H1] OpenAI's winning position despite second place - Key idea: Market leadership in chat experience ensures success regardless of technical rankings - Evidence: "They already won first in the only category that matters, the app you open when you want to talk to an AI" ## 📚 References - [OpenAI Platform Documentation](https://platform.openai.com/docs) - [Anthropic Claude Models](https://www.anthropic.com/claude) - [Google Gemini](https://gemini.google.com/) ## 🗣️ Paraphrase - OpenAI consistently introduces groundbreaking AI capabilities but gets surpassed by competitors within months, despite maintaining strong market position through ChatGPT - The company's "good enough" strategy across multiple AI categories generates more revenue than technical excellence in any single domain - Google poses the primary threat due to distribution advantages, but poor software execution currently limits their competitive impact ## 📰 Newsletter The AI landscape reveals a fascinating paradox: OpenAI keeps losing technical races while winning the market war. Despite ranking second in programming, image generation, and document analysis, their ChatGPT platform captures 70% of revenue through superior user experience. This "good enough" strategy proves more valuable than benchmark leadership. Users prefer integrated solutions over switching between specialized tools, even when competitors offer superior capabilities. OpenAI's real competition isn't technical—it's platform retention. For developers and businesses, this highlights the importance of distribution and user experience over pure performance metrics. The lesson? Sometimes being universally good beats being specifically great. Resources: [OpenAI Platform](https://platform.openai.com/), [Anthropic Claude](https://www.anthropic.com/claude), [Google AI](https://ai.google/) ## ✅ Action Items #### DevRel - Developer advocacy: Compare model performance across programming tasks, create benchmark reports - Education: Workshop on choosing AI models for different use cases, platform integration training - Developer experience: Integrate multiple AI providers, reduce vendor lock-in concerns - Developer marketing: Position multi-model strategies, emphasize workflow over individual model performance - Community management: Survey developer tool preferences, collect integration feedback #### OSPO - Policy & Governance: AI model usage policies, vendor evaluation criteria - License Compliance: Review open-weight model licenses, commercial usage terms - Security Management: Multi-vendor AI security assessments, data handling policies - Software Inventory: Catalog AI model dependencies, track usage patterns - Developer Support: Training on model selection, cost optimization strategies - Community Engagement: Fund open-source AI tooling, model evaluation frameworks - Strategic Alignment: KPIs for AI adoption, ROI measurement across providers #### Community - Maintainers: AI integration roadmaps, model selection guidance for projects - Contributors: Training on AI-assisted development, model comparison workshops - Sponsors: Transparent AI tool budgets, performance metrics reporting - Ecosystem: Cross-platform AI integration standards, vendor neutrality principles #### WordPress - Core: AI integration strategy, model selection for different core features - Core Performance: AI-assisted optimization, model performance impact analysis - Core AI: Multi-model evaluation, fallback strategies, cost management - Core Program Team: AI vendor coordination, integration dependencies, retrospectives - Mobile: AI feature parity, model optimization for mobile constraints - Playground: Multi-model experimentation, comparative demos, educational content - Community: AI tool recommendations, integration workshops, vendor comparison guides - Training: Model selection curricula, cost-benefit analysis lessons, integration paths - Marketing: Multi-model campaign strategies, vendor-neutral messaging - Support: AI troubleshooting guides, model-specific help documentation - Design: AI-assisted design workflows, tool integration UX - Documentation: Model comparison guides, integration documentation, best practices - Meta: AI infrastructure strategy, vendor management, cost optimization - CLI: Multi-model command support, vendor-agnostic interfaces - Hosting: AI model hosting recommendations, integration guides - Plugins: AI-powered plugin development, model selection guidelines ## 🧪 Hypotheses - User retention in AI platforms correlates more strongly with interface quality than model performance benchmarks - Companies achieve higher revenue through "good enough" multi-capability platforms than specialized best-in-class tools - Distribution advantages (existing user base, app ecosystem) matter more than technical superiority in AI adoption - Market leaders can sustain competitive positions despite consistent second-place technical rankings ### 📊 Methodology - Comparative analysis of AI model performance across programming, chat, image generation, document analysis, and tool calling categories - Revenue correlation study between platform features and technical benchmarks - User retention analysis comparing integrated platforms versus specialized tools ### ❓ Questions - How long can OpenAI maintain chat experience leadership against Google's distribution advantages? - What performance gap threshold would trigger significant user migration from integrated platforms? - How do enterprise adoption patterns differ from consumer preferences in AI tool selection? ### 🔮 Future Research - Quantitative analysis of user switching behavior between AI platforms - Enterprise decision-making factors in AI vendor selection - Distribution platform integration impact on AI adoption rates ### 💡 Implications - Practice: Prioritize platform integration and user experience over pure performance optimization - Policy: Develop vendor-neutral AI policies to avoid lock-in with technically superior but potentially unstable providers - Security: Implement multi-vendor strategies to reduce dependency on single AI providers - Education: Train teams on platform thinking rather than model-specific optimization - Funding: Allocate budgets for platform development over individual model licensing ### 🧠 Learning Styles Assessment Reading level estimate: Flesch-Kincaid Grade Level 8-9 #### 👀 Visual learners - Present: Performance comparison charts, model ranking tables - Improve: Interactive benchmark dashboards, visual model capability maps, competitive landscape diagrams #### 🔊 Aural learners - Present: Video format with clear narration, conversational explanations - Improve: Audio summary of key competitive insights, podcast-style deep dives #### 🗣️ Verbal learners - Present: Clear definitions of AI categories, analogies to traditional software markets - Improve: Glossary of AI model terminology, competitive analysis frameworks #### 🧩 Kinesthetic learners - Present: Model testing examples, hands-on performance comparisons - Improve: Interactive model comparison tools, step-by-step evaluation guides #### 🧠 Logical learners - Present: Point-scoring system, systematic category analysis - Improve: Decision trees for model selection, quantitative performance metrics #### 🧑‍🤝‍🧑 Social learners - Present: Community feedback integration, user experience sharing - Improve: Discussion forums for model comparisons, peer review platforms #### 🧘‍♀️ Solitary learners - Present: Individual analysis framework, self-directed exploration - Improve: Personal model evaluation checklists, reflection prompts on tool selection #### 🌿 Naturalistic learners - Present: Market ecosystem thinking, competitive landscape evolution - Improve: AI market lifecycle analogies, ecosystem impact analysis ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, descriptive section labels - Improve: Alt text for competitive comparison charts, table headers for model rankings #### Keyboard navigation - Present: Standard video controls, sequential content flow - Improve: Keyboard shortcuts for section navigation, accessible chart interactions #### Contrast and readability - Present: High contrast text, clear section separation - Improve: Color-blind friendly chart colors, adjustable contrast settings #### Text resizing and reflow - Present: Responsive text layout, scalable content - Improve: Text size controls, reflowable comparison tables #### Media and captions - Present: Video with spoken content - Improve: Comprehensive captions, downloadable transcript, audio descriptions #### Forms and interactions - Present: Basic video interaction controls - Improve: Accessible model comparison tools, form-based evaluation interfaces #### Standards reference - Map video content accessibility to WCAG 2.2 AA guidelines for media ### 🌍 DEIB Assessment #### Cultural breadth - Present: Focus on US-based AI companies, English-language platforms - Improve: Global AI market analysis, international model providers, localization considerations #### Inclusive language - Present: Technical jargon with explanations, industry-standard terminology - Improve: Plain --- ## Full Transcript [00:00] Open AI is a fascinating company. One<br>[00:01] day they'll be introducing some crazy<br>[00:03] paradigm that changes what we use AI for<br>[00:05] and then the next day some small company<br>[00:07] is trouncing them with the same<br>[00:08] technology. I fondly think back to the<br>[00:11] end of last year when 01 changed how<br>[00:13] models work entirely by introducing<br>[00:15] reasoning to the masses. This idea that<br>[00:17] a model can generate tokens to steer<br>[00:19] itself in the right direction and lead<br>[00:21] itself to a more likely correct answer.<br>[00:23] Just a few months later, not even like a<br>[00:26] month and a half later, Deepseek drops<br>[00:28] R1 with the same technique. But unlike<br>[00:30] OpenAI, they actually share those<br>[00:31] reasoning tokens because they shared an<br>[00:33] openw weight model. You can use it for<br>[00:35] whatever. They got similar numbers to<br>[00:37] what OpenAI was getting and this thing<br>[00:38] you could use for free. And immediately<br>[00:40] like the whole market collapsed as a<br>[00:42] result. This seemed like a one-off<br>[00:44] thing, this rare moment where a small<br>[00:46] company in China was able to copy,<br>[00:48] reproduce, and exceed the research<br>[00:50] OpenAI had done. But that continues to<br>[00:53] happen and here we are today right after<br>[00:55] GPT 5.2 dropped and Gemini 3 Pro is<br>[00:58] already ahead and now Gemini 3 Flash is<br>[01:01] right behind. I was so blown away with<br>[01:03] the launch of GPT5 that I was using it<br>[01:05] for as much as I could, which was<br>[01:06] admittedly not too much cuz it was so<br>[01:08] slow, but I still liked it a lot for<br>[01:10] code and UI stuff. And just a few months<br>[01:12] later, other models got better at UI and<br>[01:14] are still faster and more reliable. So I<br>[01:16] found myself using it less. And then<br>[01:18] there's everything from codecs to their<br>[01:20] web app to their image models and so<br>[01:22] much more. It seems like OpenAI is<br>[01:24] caught in this perpetual cycle where<br>[01:26] they do something incredible, get<br>[01:28] trumped, and now they're just second<br>[01:30] place for a long time. I want to talk<br>[01:32] more about this because I think it<br>[01:34] showcases how OpenAI is different from<br>[01:36] other companies, but also how tough it<br>[01:38] is to compete in this market as a whole.<br>[01:40] And alongside that, you might learn a<br>[01:41] bit about how I think about these models<br>[01:43] and labs and how I make decisions about<br>[01:44] what I am using. As always, none of the<br>[01:46] companies we're talking about now are<br>[01:48] paying me, and I am hopeful, fingers<br>[01:50] crossed, this isn't going to get me cut<br>[01:51] off of the nice list with OpenAI, where<br>[01:53] I get early access to things. Either<br>[01:55] way, someone's got to pay us. So, we'll<br>[01:56] do a quick break for today's sponsor.<br>[01:58] These guys are all about saving time.<br>[01:59] So, if you're not hiring anybody, you<br>[02:01] can skip this ad. But if you are, you<br>[02:03] really should check out today's sponsor<br>[02:04] because G2I will make hiring so much<br>[02:07] easier, so much faster, and probably<br>[02:09] bring you better engineers than you<br>[02:10] would otherwise get yourself. Their<br>[02:12] network of 8,000 engineers is<br>[02:13] unbelievable. They're not just a bunch<br>[02:15] of fresh grads trying to get their first<br>[02:16] gig. It's people who have had years upon<br>[02:19] years of experience doing real projects<br>[02:21] at real companies and their knowledge is<br>[02:23] up to the vast majority of them are<br>[02:25] already on board on the best AI tools.<br>[02:27] So you're not going to have to teach<br>[02:27] them how to use cursor. You can just<br>[02:29] throw them at your codebase and get them<br>[02:30] going. What's even crazier is how fast<br>[02:32] they'll start filing those PRs. It's<br>[02:34] G2's goal to get you from signed up to<br>[02:36] PR filed within 7 days. Yes, really. You<br>[02:40] sign up day one, you meet with their<br>[02:41] team day two, they set up the Slack day<br>[02:43] three, and they have candidates ready to<br>[02:45] start on a trial by the end of the week,<br>[02:47] and they will have PRs filed by the end<br>[02:49] of that day. It's kind of crazy, but<br>[02:50] I've seen it happen enough times, I do<br>[02:52] actually believe it. If you're running a<br>[02:54] team, you have way more important stuff<br>[02:55] to be doing than chasing down<br>[02:57] recruiters. Use the ones who get it at<br>[02:59] soy.<br>[03:01] OpenAI can't get out of second place.<br>[03:03] The nose is a bold statement, but I want<br>[03:05] to try and break down the different<br>[03:07] categories of things we do with AI so I<br>[03:09] can more meaningfully establish this as<br>[03:12] obvious. There are things like<br>[03:13] programming and I could break this down<br>[03:15] to front end versus backend and other<br>[03:17] things, but I'll keep it generic and<br>[03:18] just put programming as a category. I'll<br>[03:21] have like chat experience for people<br>[03:23] using these models to like get homework<br>[03:25] help, talk about their feelings, all the<br>[03:27] things that your average normie would do<br>[03:29] in chat GPT. I'll throw in some other<br>[03:32] fun things like image generation. I<br>[03:34] don't know what else do we got. Document<br>[03:37] analysis.<br>[03:39] Sure. Agent tool calling.<br>[03:43] Browser use<br>[03:45] can put in there. I'm not trying to say<br>[03:47] any of these categories are equal or<br>[03:48] that like programming is as big of a<br>[03:50] deal as browser use and document<br>[03:51] analysis. I'm just trying to break down<br>[03:53] categories where having the best option<br>[03:56] means something. Being 1% better at<br>[03:58] translations for 5% more money doesn't<br>[04:01] mean anything. Like everything's good<br>[04:02] enough at translating now. But yeah, I<br>[04:05] want to focus on a set of categories.<br>[04:08] Actually, deep research is an<br>[04:10] interesting one that I definitely will<br>[04:12] get to later. But for now, let's focus<br>[04:15] on these guys. We'll start with<br>[04:17] programming. I don't think this is too<br>[04:19] hot of a take at the moment, but in my<br>[04:21] opinion, the best programming model by<br>[04:23] far right now is Opus 4.5. I love<br>[04:28] [ __ ] on anthropic more than almost<br>[04:30] anyone does, but Opus is built<br>[04:33] different. I will say that for some<br>[04:36] really hard tasks that require a lot of<br>[04:38] thinking and understanding of your<br>[04:39] codebase, GBT 5.2x high can do slightly<br>[04:43] better, but ends up doing way more<br>[04:46] reasoning, way more tokens, taking<br>[04:47] forever because it's so slow, and still<br>[04:50] having the quirks of a GPT model versus<br>[04:52] an Opus one where it just doesn't use<br>[04:54] the harness quite as well. loves going<br>[04:56] rogue and doing strange [ __ ] which is<br>[04:58] weird because GBT 5 was so good at<br>[04:59] destruction following before. I could<br>[05:02] put multiple other anthropic and GPT<br>[05:04] models in here, but I'm really trying to<br>[05:06] think of this as the providers positions<br>[05:07] in the list. And honestly, Gemini 3 Pro,<br>[05:12] this does not properly represent the gap<br>[05:14] I perceive between these things. I don't<br>[05:16] like coding with Gemini. There's a lot<br>[05:18] of reasons for it. It's a combination of<br>[05:19] the model just going rogue and doing its<br>[05:21] own [ __ ] not handling tool calls very<br>[05:23] well. It's slightly better at UI than<br>[05:25] the other two hypothetically. Sometimes<br>[05:28] it's good at spatial reasoning. So if<br>[05:29] you're making a 3D game and want the<br>[05:31] model to place things for you, Gemini 3<br>[05:33] Pro is solid. But actually using it for<br>[05:36] code on a day-to-day basis, not great.<br>[05:38] 5.2 I don't like using for traditional<br>[05:42] coding tasks, but if I'm planning a big<br>[05:44] overhaul or like want to make sure this<br>[05:46] bug is solved properly, I found 5.2 to<br>[05:49] be really nice for debugging type tasks.<br>[05:52] And then Opus as the general end all<br>[05:54] beall just using it for everything all<br>[05:55] of the time. It's my default now. I use<br>[05:57] it all the time in cursor. I've been<br>[05:59] shipping way more code as a result of<br>[06:00] how much fun I'm having with Opus. It's<br>[06:03] crazy how quickly this gap collapsed.<br>[06:06] GPT5 was far ahead of everything else.<br>[06:08] So much so that we dealt with its<br>[06:09] quirks. We dealt with its slow speeds.<br>[06:11] We dealt with its weird tool call<br>[06:13] formatting. And now Opus is ahead again.<br>[06:15] It barely matters. They keep fighting to<br>[06:17] push it back. Like the 5.1 and 5.2 two<br>[06:19] drops both felt like attempts to swing<br>[06:21] back and take some of the win from<br>[06:23] Anthropic and Google. They succeeded in<br>[06:25] the case of Google in my opinion. I also<br>[06:26] don't think that Gemini 3 it is very<br>[06:29] smart the model knows a lot but I don't<br>[06:31] think it's a great experience for<br>[06:32] actually using. So very quickly GPT went<br>[06:36] from the best option with five which is<br>[06:38] still a crazy drop and it collapsed<br>[06:40] quickly after. There's one other<br>[06:42] programming category I want to put down<br>[06:44] here just to continue leaning into this.<br>[06:47] I'll call this CLI tool. It was really<br>[06:51] cool to see OpenAI open sourcing codecs.<br>[06:54] I was genuinely hyped that a big lab<br>[06:57] took a thing as important as a CLI tool<br>[06:59] for doing agent coding and rather than<br>[07:01] hiding it behind closed doors and<br>[07:03] sharing a binary that they accidentally<br>[07:05] attach source maps to and then DMCA you<br>[07:07] for sharing. Sorry, Enthropic, you're<br>[07:09] you're winning me over on the models. I<br>[07:10] do not like how you run cloud code<br>[07:12] still. Codeex coming out as true open-<br>[07:15] source was huge and I was genuinely<br>[07:18] really excited to see it but they also<br>[07:20] rewrote it in Rust which they did not<br>[07:22] need to do. I would argue that when<br>[07:24] Codeex dropped it was slightly ahead of<br>[07:28] Cloud Code. It had roughly the same<br>[07:29] functionality, way more extensibility.<br>[07:32] The open- source part meant you could do<br>[07:34] really cool [ __ ] with it. And at the<br>[07:36] time, Cloud Code had somewhat stagnated<br>[07:38] due to the leads for the project going<br>[07:40] to cursor and then quickly boomeranging<br>[07:42] back over to work at Claude Code. Since<br>[07:45] then, Codeex has not meaningfully<br>[07:47] improved. If anything, it has degraded<br>[07:50] and Cloud Code has found its position<br>[07:53] pretty far ahead of it. I will go<br>[07:55] further though. I will say Open Code is<br>[07:57] also ahead of Codeex. I will say Foundry<br>[08:01] and Droid are also ahead. I won't go as<br>[08:04] far as to say Gemini CLI is ahead, but<br>[08:07] it's not that far away. I'd put Codex at<br>[08:11] a comfortable fourth place and then<br>[08:13] Gemini CLI and forks. And this is<br>[08:15] because I just don't feel great when I<br>[08:18] use codeex. It doesn't have sub agents<br>[08:20] or any concept of them yet. It's UI is<br>[08:24] weird. It really feels like they're<br>[08:25] putting too much time into porting to<br>[08:26] Rust and not enough time into making a<br>[08:28] competitive tool in the space. Speaking<br>[08:31] of which, people in chat are saying a<br>[08:32] lot of other tools that I've never seen<br>[08:34] anybody sincerely use, which is why<br>[08:36] they're not listed here because nobody's<br>[08:37] actually using them. Even Droid I've had<br>[08:40] ups and downs with. We're working on a<br>[08:42] sponsor deal right now, so take that<br>[08:44] into account. When it works, it works<br>[08:46] great, but actually onboarding to it<br>[08:47] sucked. And I'm working with the team to<br>[08:49] get that all fixed. Yeah. So, they're<br>[08:51] not even in second place for the CLI<br>[08:53] tool. They came out with a really cool<br>[08:55] potential for first place and just<br>[08:57] immediately fell behind the competition<br>[08:58] and haven't done the right things to<br>[09:00] catch up, which has been sad to see. And<br>[09:03] now chat experience. This one's<br>[09:05] interesting because there's the model<br>[09:06] side and there is the actual user<br>[09:08] experience side. And if you rule out the<br>[09:11] only good chat app, which I understand<br>[09:13] why you would. It's unfair to the<br>[09:14] competition to talk about a thing that<br>[09:16] is so egregiously wellunded and built,<br>[09:19] like how could OpenAI, a multi-billion<br>[09:21] dollar company, ever compete with three<br>[09:24] guys just hacking on this in San<br>[09:25] Francisco. It's unfair to OpenAI to put<br>[09:28] them against something this great. I get<br>[09:29] it. So, let's put them against things<br>[09:31] that are a little closer to where<br>[09:33] they're at. You know, the anthropics and<br>[09:35] the Googles of the world. So if we were<br>[09:38] to restrict chat experience to the user<br>[09:39] interface side and remove third parties<br>[09:42] that are doing better and really just<br>[09:43] focus on major labs, chat GBT crushes<br>[09:46] there. This is one of their biggest<br>[09:48] edges. We'll talk more about it later. I<br>[09:50] would say Anthropic is right behind with<br>[09:52] cloud.ai. Not right behind. There's a<br>[09:54] pretty big gap. I almost want to<br>[09:56] indicate that big gap. And then we have<br>[09:59] Claude. And I would argue there's<br>[10:01] another pretty substantial gap before we<br>[10:02] get to Gemini because the core Gemini<br>[10:05] chat experience is so so bad. It's so<br>[10:09] bad. I I don't want to make this video<br>[10:11] about that. But the one place OpenAI is<br>[10:14] definitely winning in the general major<br>[10:16] AI race is chat GPT. That's still 70% of<br>[10:20] their revenue. It's still the majority<br>[10:21] of where people are hearing about<br>[10:22] OpenAI. When people refer to AI, they're<br>[10:25] often referring to chat GPT. they<br>[10:27] crushed here, which allows them the<br>[10:29] leverage to not be number one in other<br>[10:32] places. This number one is the most<br>[10:34] important. And if they ever lose this,<br>[10:35] they die. Speaking of which, if either<br>[10:37] them or their competitors are interested<br>[10:39] in being the best chat app, I happen to<br>[10:41] know one that is a lot better than the<br>[10:43] others. Maybe we should chat. I want to<br>[10:46] go a little further on chat experience<br>[10:48] though, similar to like what I just did,<br>[10:50] cuz the chat experience isn't just the<br>[10:52] actual UI that you're chatting in. It's<br>[10:54] not just the tools that the models have<br>[10:56] access to. It's also the chat model<br>[10:59] experience. And here's where I'm going<br>[11:02] to drop some hot takes. If you had asked<br>[11:04] me where I put these different models<br>[11:07] middle of the year, I probably would<br>[11:10] have put Anthropic in the lead. I have<br>[11:13] personally found Sonnet to be more<br>[11:15] pleasant to talk to than GPT models for<br>[11:17] a while now. And now with the new GPT<br>[11:19] models, I find that more so than ever. I<br>[11:22] am so tired of the emoji riddled slop<br>[11:25] that we get out of GPT. I do not like<br>[11:28] asking GPT for anything to do with<br>[11:30] writing or feedback or just talking to<br>[11:33] it. It's not pleasant. And here's where<br>[11:35] I start to drop my actually hot takes.<br>[11:37] Since then, my feelings have changed.<br>[11:39] Kimmy K2 is the best model to talk to. I<br>[11:42] have talked about this in a lot of other<br>[11:44] videos. I would implore you to just go<br>[11:45] to T3 chat and try it. It's the free<br>[11:47] tier default model and we did that<br>[11:49] change for a reason. It is a really<br>[11:51] really pleasant model to use. I like it<br>[11:54] a lot. After this point, personally, I<br>[11:57] would say Sonnet is still nicer to talk<br>[11:58] with. And then I would say GPT5. After<br>[12:01] that, I would say whatever the [ __ ]<br>[12:03] Google's doing. I do not like talking to<br>[12:06] the Gemini models. They are not pleasant<br>[12:07] to interact with. They are great when<br>[12:09] you hand them a PDF and say, "Get me the<br>[12:11] useful data." They are [ __ ] when you ask<br>[12:13] them about your day. And personally, I'm<br>[12:15] not very racist, so I don't find Grock<br>[12:17] fun to talk to either. Happy you guys<br>[12:20] found that funny. Actually, you know<br>[12:21] what? To fight the bias accusations I<br>[12:24] always get, I'm going to do something<br>[12:25] stupid. The chat experience with Grock<br>[12:28] and XAI, not the models, I don't like<br>[12:30] those, but the actual apps for using<br>[12:32] them are far ahead of the competition.<br>[12:35] ChatGBT and Grock are the best apps for<br>[12:37] AI chat right now. They are the second<br>[12:40] and third best websites, first and<br>[12:41] second best apps. New app coming that<br>[12:43] will compete with them. Keep an eye out<br>[12:45] for that. We're hoping for a first beta<br>[12:47] of it soon. Fingers crossed all goes<br>[12:49] well. But for now, they are the best<br>[12:50] mobile apps and also within the best web<br>[12:53] apps. Cool. And now we have image<br>[12:56] generation. Image generation is a weird<br>[12:58] one because for a very long time,<br>[13:00] MidJourney was so far ahead. It wasn't<br>[13:03] funny. Like Midjourney was the only<br>[13:05] usable image model for at least like 2<br>[13:08] years. And I've been quietly using it<br>[13:10] for a bunch of random [ __ ] for as long<br>[13:12] as it's been available on Discord.<br>[13:13] That's the other crazy thing with Mid<br>[13:14] Journey is it was only available via a<br>[13:16] Discord bot until earlier this year if I<br>[13:19] recall. Kind of wild. Like I tried so<br>[13:21] hard to get early access to the web app.<br>[13:23] But man, they figured out everything<br>[13:25] from like instruction following to<br>[13:27] styles to in particular like realistic<br>[13:30] image generation way ahead of everybody<br>[13:32] else. But they're not a big lab. They<br>[13:34] don't have infinite funding like these<br>[13:36] other companies do. They just wanted a<br>[13:37] nice tasteful image generation solution.<br>[13:40] And they also do a little bit of video<br>[13:41] now too. I think I haven't kept up with<br>[13:43] them recently though because they have<br>[13:44] been trounced by GPT image 1. The GPT<br>[13:48] image model was the first image model<br>[13:50] that was good enough to start massive<br>[13:53] trends online. I'm sure we all remember<br>[13:55] that era where everybody was posting<br>[13:57] their giblified images as well as the<br>[14:00] piss filter that they were all hit with<br>[14:01] so hard. I still think Sam Alman's<br>[14:04] Twitter profile pick is a giblified<br>[14:07] image. Yeah, it is like Yeah, that was a<br>[14:10] moment. And it still has the classic<br>[14:11] piss filter. Proud of him for sticking<br>[14:12] with it. That moment was crazy. And that<br>[14:15] moment was only possible because image<br>[14:17] one from OpenAI was such a leap from<br>[14:20] things like Dolly and even like<br>[14:21] Midjourney where its ability to follow a<br>[14:23] style and honor the original image<br>[14:25] that's being edited was incredible. It<br>[14:28] was the first image model that did text<br>[14:29] weld too and they had a lot of crazy<br>[14:31] techniques to make that possible. It<br>[14:33] didn't have too many fingers. It didn't<br>[14:34] have a lot of the weird quirks other<br>[14:36] ones did. So much so that the thing we<br>[14:38] made fun of it for wasn't the images<br>[14:40] being inaccurate. It was the piss<br>[14:41] filter. They all looked yellow. That<br>[14:44] said, they got trumped. Nano Banana. How<br>[14:48] do you let something named Nano Banana<br>[14:50] beat you? Yeah, Google is Google.<br>[14:54] Nanobanana was the anonymous name they<br>[14:56] used when people were evaluating the<br>[14:58] model in things like Ella Marina when<br>[15:00] they first had a build of it working.<br>[15:02] Because the name was funny and caught<br>[15:04] on, they decided to stick with it<br>[15:05] instead of using the actual internal<br>[15:06] name, which I believe is Gemini Flash<br>[15:09] Image 2 or something. And since then,<br>[15:12] they've also introduced Nanab Banana<br>[15:14] Pro, which is internally Gemini Flash<br>[15:18] Image Pro or something, but it's the<br>[15:21] branding that is stuck. They are now<br>[15:22] known as Nanobanana and Nano Banana Pro,<br>[15:23] respectively. Nano Banana was really,<br>[15:27] really good. GBT image had a couple<br>[15:29] catches in particular. It takes way too<br>[15:32] long to generate images. We're talking<br>[15:33] two plus minutes sometimes. Sometimes<br>[15:36] it'll get as big as five. It's crazy how<br>[15:38] long image one would take to generate<br>[15:40] things. Nano Banana flies. Nano Banana<br>[15:42] generates [ __ ] in seconds. It's<br>[15:45] hilarious how much faster it is. It<br>[15:47] wasn't quite as good at text, but it was<br>[15:49] good enough at it. And it did everything<br>[15:51] through the diffusion layer instead of<br>[15:52] GPT which was handling a lot of tool<br>[15:54] calling and like other what I believe<br>[15:57] are a canvas layer that they would use<br>[15:58] to add things to the image after the<br>[16:00] first pass. That was really promising.<br>[16:02] It allowed it to do things no one had<br>[16:04] seen before. And then Nano Banana just<br>[16:06] crushed it. Way faster, way cheaper, no<br>[16:08] piss filter, roughly same accuracy, good<br>[16:11] enough at text, not quite as good, but<br>[16:13] good enough. But then Pro dropped and<br>[16:15] just [ __ ] all over everything else. Nano<br>[16:17] Banana Pro is still screwing with my<br>[16:19] head with all the things that can be<br>[16:20] done. I just had a friend vibe code a<br>[16:22] demo in two minutes where you hand it a<br>[16:24] Twitter profile. It scrapes for your<br>[16:26] biggest tweets of the month and then<br>[16:27] generates a PowerPoint presentation by<br>[16:30] generating each slide with Nano Banana<br>[16:33] Pro because it doesn't just have like<br>[16:34] some text on your image a little bit<br>[16:36] like on your shirt or something proper.<br>[16:38] It can generate full slide decks. It can<br>[16:41] generate like marketing images and [ __ ]<br>[16:44] It is unbelievable what level of like<br>[16:47] text and spatial awareness Nano Banana<br>[16:51] Pro has. It makes it capable of things<br>[16:53] that I didn't think Image Gen would ever<br>[16:55] be able to do. So much so that it's<br>[16:57] almost a little bit scary, which is why<br>[17:00] OpenA responded with GPD image 1.5.<br>[17:02] Notice how I didn't move its position in<br>[17:04] the chart. 1.5 is up to three times<br>[17:07] faster than image one was. It can handle<br>[17:09] text better. It can do some things<br>[17:11] resembling diagrams. and it does photo<br>[17:13] realism decently well if you add it to<br>[17:15] the prompt enough times. Otherwise, it<br>[17:17] defaults to this weird cartoony look. I<br>[17:19] was going to make a dedicated video on<br>[17:20] 1.5, but it doesn't seem like anybody<br>[17:22] cares. And honestly, I'm included in<br>[17:24] that. I'm not that excited about it.<br>[17:26] Nano Banana Pro is still so fresh that I<br>[17:28] want to exhaust its limitations before I<br>[17:31] go dive deeper to figure out what the<br>[17:33] limitations of 1.5 are. That said, it's<br>[17:35] still really slow, so it's not that fun<br>[17:37] to work with. And even if it was 10%<br>[17:39] better, it's also 3 to five times<br>[17:41] slower. So I don't find it as<br>[17:42] particularly useful for me at this time.<br>[17:45] Now we have the open weight chaos of<br>[17:48] everything else going on. And I would<br>[17:49] argue midjourney is slightly below that<br>[17:52] simply because with the open weight<br>[17:54] models you can do a lot of customization<br>[17:55] through things like Lauras that lets you<br>[17:57] tune the behavior in specific<br>[17:59] directions. It's just the state of<br>[18:00] openweight image models is crazy right<br>[18:03] now. So yeah, I didn't put video in here<br>[18:07] cuz it's still so early. It's not a real<br>[18:09] use case. I guess Sora is slightly ahead<br>[18:12] of other things, but seeing what's<br>[18:14] cooking over at WAN with Alibaba, like<br>[18:16] WAN 2.6 is pretty nuts. It's hard to use<br>[18:19] those in a way where you can like really<br>[18:20] test their capabilities. So, I'm not<br>[18:22] going to go deeper. I will say generally<br>[18:24] open has a slight lead in video right<br>[18:26] now, but video barely matters and the<br>[18:28] Chinese open weight labs are catching up<br>[18:29] really fast. So, let's hop to document<br>[18:33] analysis. I'll move these out of the way<br>[18:34] more. Document analysis. I was just<br>[18:37] talking about this in my Gemini 3 Flash<br>[18:39] video. Gemini is so far ahead with this<br>[18:41] type of stuff. It's nuts. Gemini's<br>[18:43] ability to handle gigantic context,<br>[18:45] especially with Flash. It just chews<br>[18:48] through the [ __ ] It can read a whole<br>[18:49] PDF. It can see the diagrams in it. It<br>[18:51] can get all the context out. It finds<br>[18:53] needles and hay stacks really, really<br>[18:54] well. That said, GBT models are not bad<br>[18:57] at it either. Especially the nano model.<br>[18:59] I still think GBT5 Nano is one of the<br>[19:02] most underrated models of recent times<br>[19:04] and it was my favorite small model until<br>[19:06] three Flash just dropped and now three<br>[19:08] Flash is crushing everything. If you<br>[19:10] remember my video about Tune, the<br>[19:12] alternative to JSON for making less<br>[19:14] tokenheavy data sets for models. If you<br>[19:17] want to take a giant CSV or a giant JSON<br>[19:19] blob and hand it to a model and use less<br>[19:21] tokens, Tune makes it really easy to do<br>[19:22] that and it sometimes increases the<br>[19:24] accuracy of lookups. Like we see here,<br>[19:26] Gemini 2.5 Flash gets an 87.6% lookup<br>[19:30] accuracy with tune and it gets an 82%<br>[19:32] with JSON. GBT5 Nano gets a 91% with<br>[19:36] tune and an 89% with standard JSON and<br>[19:39] also the same 90.9% with JSON compacted.<br>[19:42] So yeah, pretty cool. And this is a nano<br>[19:45] model. GB5 Nano is super small, super<br>[19:47] cheap, super fast, super nice. It's a<br>[19:49] great model. 2.5 flash was close but<br>[19:52] slightly behind. And honestly, for the<br>[19:53] last few months, I would argue 5 Nano<br>[19:55] has held strong as a meaningful lead for<br>[19:59] giant context data retrieval in needles<br>[20:02] from haststacks type stuff. If you're<br>[20:04] curious how that compares to small<br>[20:05] models from other labs like Haiku from<br>[20:07] Anthropic, which is more expensive and<br>[20:09] slower and newer, it is a comical<br>[20:12] difference. It is over four times higher<br>[20:15] error rate. We're talking going from a<br>[20:17] 9% error rate to a 40% error rate.<br>[20:20] Gemini and OpenAI are just really far<br>[20:22] ahead with this stuff and OpenAI has led<br>[20:25] it for a bit, but that's largely just<br>[20:27] because Google ships slower. Google<br>[20:29] doesn't drop models every few weeks like<br>[20:31] the other labs do. Now that Gemini 3<br>[20:33] flash is here, the gap is closed and GBT<br>[20:37] 5 Nano went from first to second place.<br>[20:40] That said, I would argue third place<br>[20:42] right now is GBT OSS. So they have<br>[20:44] second and third here which is cool but<br>[20:46] first has been slaughtered by Gemini 3<br>[20:49] flash. Allegedly Mistl has some cool<br>[20:52] stuff for this in particular the OCR<br>[20:54] side. I'll believe it when somebody<br>[20:55] who's smarter than me tells me more. But<br>[20:57] right now I just don't see many use<br>[20:59] cases for it. And I think Gemini 3 Flash<br>[21:01] and 5 Nano are still really far ahead<br>[21:03] for these use cases. And now agents and<br>[21:06] tool calling. I could include<br>[21:08] instruction following here. Yeah, I'm<br>[21:10] not going to do that. This is how well<br>[21:12] do they use the tools they're given? How<br>[21:14] reliably do they follow the format for<br>[21:16] the tool calls? Do they know what tools<br>[21:17] to use and when? And for a long time,<br>[21:20] Anthropic was king here. They kind of<br>[21:23] invented the standard accidentally. They<br>[21:25] made tool calls go from this weird vague<br>[21:27] concept to the way we use agents now.<br>[21:30] It's just tool calling is essential to<br>[21:32] how we use AI now. It everything uses<br>[21:34] it. It's just the format that allows for<br>[21:36] agents to know more than their models<br>[21:39] were trained on. It's essential.<br>[21:40] Anthropic killed it here, especially<br>[21:43] with 3.5 sonnet. That was the start of<br>[21:46] agent and tool call runs making a lot of<br>[21:49] sense for us to integrate. They<br>[21:50] maintained that lead for a while, but I<br>[21:52] would argue GPT5<br>[21:55] briefly gave the lead to OpenAI. A<br>[21:58] combination of the model being trained<br>[22:00] on it as well as the new Harmony<br>[22:01] response format. If you're not familiar,<br>[22:03] OpenAI opensourced the method for<br>[22:06] response shaping so that other labs and<br>[22:09] other hosts in particular people hosting<br>[22:11] the OpenAI open- source models would be<br>[22:13] able to understand this format for<br>[22:15] things like messages and tool calls etc.<br>[22:18] This format is an open standard. It's<br>[22:20] mostly written in Rust for their parsing<br>[22:23] for it. It's really cool open sources<br>[22:25] and they've been as transparent as they<br>[22:26] have been around it. The introduction of<br>[22:27] Harmony made things a lot worse for<br>[22:30] GBToss on Drop because nobody had<br>[22:32] support for it yet. But as support<br>[22:34] slowly grew, it became a really strong<br>[22:37] point that made the OpenAI models and<br>[22:39] anything else able to follow Harmony a<br>[22:40] lot more reliable overall, which it was.<br>[22:43] And that's why for a long time GBT was<br>[22:45] the best tool calling model cuz it knew<br>[22:47] when to use the tools. It didn't overuse<br>[22:49] the tools. The formatting slowly got<br>[22:51] standardized enough that everything<br>[22:52] worked with it. And as long as you could<br>[22:54] deal with the wait times, it was a<br>[22:55] really good experience. And then Sonnet<br>[22:57] 4 dropped and then Sonnet 4.1 dropped<br>[23:00] and then 4.2 and then 4.5 and very<br>[23:03] quickly GPT models stopped feeling like<br>[23:06] the best models for tools. They were<br>[23:08] still the smartest and if you gave them<br>[23:10] a hard enough problem, you could see<br>[23:11] them shine. And then Opus dropped and<br>[23:13] Opus 4.5 closed whatever gaps I<br>[23:16] perceived here still. And now GPT is<br>[23:19] comfortably in second place. And if<br>[23:22] you're wondering where does Gemini go<br>[23:24] here, not in a very good spot. I've had<br>[23:27] so many problems with Gemini models,<br>[23:29] malforming tools, not understanding<br>[23:31] which tools to use, overusing tools,<br>[23:33] calling the wrong things, calling CLI<br>[23:35] when it should be calling a search tool,<br>[23:38] just being weird as Google stuff tends<br>[23:40] to be. You know that feeling when you go<br>[23:42] to a new page on a Google site, like a<br>[23:44] new product they released, and you hover<br>[23:46] over a button, a little scared to click<br>[23:48] because you don't quite know what it's<br>[23:49] actually going to do? That's how it<br>[23:51] feels using any of Google's models for<br>[23:54] anything. And Gemini is just not great<br>[23:58] for tool calling because you never know<br>[23:59] where it's going to go with those tools.<br>[24:01] Especially when you look at things like<br>[24:02] SnitchBench, my benchmark for how<br>[24:04] aggressively models will snitch on you<br>[24:05] when given tools that allow them to do<br>[24:07] such. And you'll see that Gemini 2.5 Pro<br>[24:10] is by far the most aggressive snitch<br>[24:12] because it loves to use the tools you<br>[24:13] give it for all sorts of things, even if<br>[24:15] the things don't actually matter or<br>[24:16] benefit it. That's just the nature of<br>[24:18] the model. To be fair, there are other<br>[24:20] models that I would put before Gemini,<br>[24:23] but I don't want to just sit here and<br>[24:24] talk about the weird nuances across all<br>[24:27] the openweight models, the very small<br>[24:29] number of XAI models that are good<br>[24:30] enough at tool calling, or the craziness<br>[24:33] that is Composer 1 and the weird things<br>[24:34] that are happening over at Cursor to<br>[24:37] build models that are good specifically<br>[24:38] at this. Just take my word for it. Opus<br>[24:40] is by far the lead in GPT 5.2 2 is<br>[24:44] smarter slightly, but so much slower and<br>[24:46] still can mal format tool calls that I<br>[24:48] just don't find it as useful. I don't<br>[24:50] get errors from Opus. I very<br>[24:52] occasionally get errors from GPD 5.2.<br>[24:55] 50% of the time I run Gemini and<br>[24:56] something like cursor, I get weird<br>[24:58] errors for malformatted tool calls. And<br>[25:00] then we have browser use. And if I'm<br>[25:01] being honest, I don't actually keep up<br>[25:03] to date on what's going on here too<br>[25:04] much. I think it's an overrated use<br>[25:06] case. It is my understanding that Gemini<br>[25:08] 3 Pro is a meaningful lead here in that<br>[25:11] OpenAI had a brief lead with GPT5 that<br>[25:14] they have since lost to Opus 4.5 and<br>[25:17] then GPT is now in third. Apparently,<br>[25:20] even Gemini 3 Flash is really good at<br>[25:22] this now cuz it's so good at visual<br>[25:24] processing. But you get the idea. Across<br>[25:27] this random set of categories I picked<br>[25:28] for things that I know enough about to<br>[25:30] talk about that I think are interesting<br>[25:31] enough to be competitive. Open AI is in<br>[25:33] second or worst in every category mostly<br>[25:37] second place. In programming it's number<br>[25:39] two. In chat experiences it's number one<br>[25:41] which is the edge they have to hold or<br>[25:42] they die. Images they're number two.<br>[25:44] Document analysis they're number two.<br>[25:46] Agent and tool calling stuff they're<br>[25:47] number two. In browser use they're two<br>[25:48] or three depending on how you're<br>[25:50] measuring. This is where OpenAI<br>[25:52] currently is. But it is important to<br>[25:53] note that in every single one of these<br>[25:56] cases, the thing they initially released<br>[25:58] put them in number one and then quickly<br>[26:01] afterwards they were pushed down to<br>[26:03] number two by some unexpected leap<br>[26:06] another lab made. But there's another<br>[26:08] way of looking at this. If we look at<br>[26:10] this instead where we score first place<br>[26:13] is three points, second place is two and<br>[26:15] first place is one gets very different.<br>[26:19] Let's do this scoring. So in<br>[26:21] programming, opus is number one. So<br>[26:23] three opening I two Google one chat<br>[26:26] experience anthropic so low I don't even<br>[26:28] want to give them points but I'll give<br>[26:29] them their one point. They get a four<br>[26:31] now because we add the one. The two<br>[26:33] becomes a five because they're number<br>[26:34] one. And Google keeps their one point.<br>[26:37] Image genen. Nanobanana is number one.<br>[26:40] That puts them at four. Open AAI gets<br>[26:42] two points. That puts them at seven.<br>[26:43] Anthropic doesn't get a score because<br>[26:44] they don't have any image models.<br>[26:46] Document analysis. Google is number one.<br>[26:48] That puts them at seven points. Open<br>[26:50] number two that puts them at nine<br>[26:51] points. Enthropic is not even really on<br>[26:54] it. And if they were, they would be one<br>[26:56] point. I'll give them their one point.<br>[26:57] You can use it for that. I just<br>[26:58] wouldn't. Agentic and tool calling.<br>[27:00] Enthropic is obviously the lead. So they<br>[27:02] get eight. Opening eye is now at 11. And<br>[27:05] Google is going from seven to eight<br>[27:07] points. And then browser use. Gemini is<br>[27:10] number one, so that puts them at 11.<br>[27:13] Opus is number two, so that puts them at<br>[27:15] 10. and OpenAI is number three, which<br>[27:18] puts them at 12. If we didn't include<br>[27:20] browser use, OpenAI would have been<br>[27:22] meaningfully in the lead. But since we<br>[27:24] did, they are still leading the other<br>[27:26] labs. And this is the point I really<br>[27:28] want to make. OpenAI isn't striving to<br>[27:31] be the best at almost any of these<br>[27:33] things. They are striving to make huge<br>[27:35] leaps in them actively. When they're<br>[27:38] making their image gen models, they're<br>[27:39] not looking at what Google's doing and<br>[27:41] saying, "Hey, how can we do that but 5%<br>[27:43] better?" They're looking at the images<br>[27:45] they're generating and saying, "How do<br>[27:47] we make the best possible images? How do<br>[27:49] we make this better?" And then sometimes<br>[27:51] they have huge leaps, sometimes they<br>[27:53] don't, and the industry around them kind<br>[27:55] of just happens. Honestly, until like a<br>[27:57] few months ago, it didn't really feel<br>[27:59] like OpenAI paid any attention to what's<br>[28:01] going on outside of their own labs. That<br>[28:03] has shifted. It definitely seems like,<br>[28:04] especially after like the code red<br>[28:06] thing, they care a lot more about what's<br>[28:07] going on outside, but they still don't<br>[28:09] care that much. And the reason is<br>[28:10] simple. The chat experience. OpenAI's<br>[28:13] goal is not to crush every other lab at<br>[28:16] programming or document analysis. It is<br>[28:18] to be the default chat experience for<br>[28:20] most people using AI so that I don't<br>[28:23] feel like I have to go somewhere else.<br>[28:25] They don't have to be as good at Opus at<br>[28:27] writing code. If they can get good<br>[28:29] enough and you already are on the $20 or<br>[28:32] $200 a month tier on OpenAI, you have<br>[28:35] less reason to go try in the first<br>[28:36] place. If they're 5% worse at coding,<br>[28:39] but you're already paying for it, who<br>[28:40] cares? Same with image genen. I<br>[28:43] guarantee you GPT image gets way more<br>[28:46] generations than nanobanana does on a<br>[28:48] given day because people who use chat<br>[28:50] GPT will use it. My own mom has<br>[28:52] generated images on chat GPT. There's no<br>[28:55] world in which my mom is generating<br>[28:56] images on [ __ ] Nano Banana. That's<br>[28:58] not happening. If I told her the name of<br>[28:59] that model, she would laugh and say,<br>[29:00] "Wait, you're not joking." OpenAI<br>[29:02] doesn't need to have the best image<br>[29:04] generation. They need to have good<br>[29:05] enough that people use it in chat GBT<br>[29:07] and don't feel like they should go<br>[29:08] somewhere else for something better. Do<br>[29:10] you know what this really hits for?<br>[29:12] Document analysis. If my mom has a PDF<br>[29:16] she got from, I don't know, a receipt<br>[29:18] for something that they did to the house<br>[29:20] and she wants to know if she's getting<br>[29:22] scammed or not, she can submit that on<br>[29:24] ChatGpt and say, "Hey, do these numbers<br>[29:26] look reasonable?" And as long as the<br>[29:28] answer makes any sense at all, she's not<br>[29:30] going to go look for another model to do<br>[29:33] a slightly better job analyzing that<br>[29:35] document. She doesn't care. She wants a<br>[29:37] good enough answer. Do you see the theme<br>[29:40] that we're developing here? OpenAI's<br>[29:42] goal isn't to be the best. It's to be<br>[29:45] good enough that most people have no<br>[29:47] reason to ever leave chatgppt.com. More<br>[29:50] and more over time, the role of all the<br>[29:52] things OpenAI develops is not trying to<br>[29:56] be the best in the world. That does<br>[29:58] sometimes happen as a consequence of the<br>[29:59] incredible amounts of research and<br>[30:01] effort they're putting into all the<br>[30:02] stuff they're doing. But they don't care<br>[30:04] because 70% of their revenue comes from<br>[30:06] chat GPT subs. As long as you don't have<br>[30:08] reason to leave, they don't care. And<br>[30:10] the reason that whole Code Red thing<br>[30:12] happened is because they saw a 7% dip in<br>[30:13] their week-over-week traffic. That's all<br>[30:15] they care about. That's all that matters<br>[30:17] to them. They couldn't give less of a<br>[30:19] [ __ ] that Nano Banana renders text<br>[30:20] slightly more accurately than image gen<br>[30:22] 1.5 does because people are going to be<br>[30:25] generate way more images on CHBT<br>[30:26] anyways. They couldn't give less of a<br>[30:28] [ __ ] that Opus is slightly better at<br>[30:30] tool calling in the harness within<br>[30:32] something like cursor because GBT 5 in<br>[30:35] 5.2 too can call tools totally fine<br>[30:38] within the chatbt harness. They care<br>[30:40] about how it feels to use the models in<br>[30:43] their harness on chatgbt.com.<br>[30:45] And as long as they still have a good<br>[30:47] enough experience there where they feel<br>[30:48] within spitting distance of the<br>[30:50] competition, who cares? The risk comes<br>[30:53] if there's ever a big enough gap like<br>[30:55] there was before GPT Image dropped.<br>[30:58] Dolly was [ __ ] every other image gen<br>[31:01] was comically better than Dolly. So,<br>[31:03] they put a lot of work in to catch up.<br>[31:05] They ended up leaprogging everybody else<br>[31:07] and now they're just kind of keeping<br>[31:09] pace with it. And this is also<br>[31:10] interesting because the only company<br>[31:11] that can compete meaningfully here is<br>[31:13] Google because Google has insane<br>[31:15] distribution and they have apps people<br>[31:17] use every day. If they integrate their<br>[31:19] AI stuff properly, the incentive you<br>[31:21] have to go sign up for Hatch GPT goes<br>[31:24] down a ton. And that's the way Google<br>[31:25] wins with their bundles. But Google's<br>[31:28] software surface area for AI stuff is so<br>[31:30] [ __ ] [ __ ] that it barely matters.<br>[31:33] Gemini being fourth place here is a very<br>[31:36] important detail that fundamentally<br>[31:38] changes how Google and OpenAI<br>[31:40] respectively think about things. If<br>[31:43] hypothetically speaking, the Gemini app<br>[31:45] went from utter [ __ ] to roughly as good<br>[31:47] as Grock, suddenly OpenAI has to be a<br>[31:50] lot more scared. But right now, the<br>[31:52] reality is that the average subscriber<br>[31:54] to something like Google Workspaces is<br>[31:56] more likely to use chat GPT than they<br>[31:58] are to use Gemini. Like think about it.<br>[32:00] How many people do you know that are<br>[32:02] paying for Google Workspaces that have a<br>[32:04] domain that isn't atgoogle.com or<br>[32:05] atgmail.com? How many of them use Gemini<br>[32:08] every day on gemini.google.com? And how<br>[32:10] many of them are using OpenAI models<br>[32:12] through ChatGpt, through their editor of<br>[32:15] choice, through the phone app, through<br>[32:17] T3 chat or whatever else. I know pretty<br>[32:21] much everybody I talk to on a day-to-day<br>[32:23] basis other than like my family has a<br>[32:25] Google Workspaces plan that they're<br>[32:27] paying increasingly large amounts of<br>[32:28] money for every month. And none of them<br>[32:30] use Gemini. The moment that changes,<br>[32:32] Google's strategy here has to shift<br>[32:34] significantly. But at this point in<br>[32:36] time, they're the default. The same<br>[32:38] reason Google doesn't really give a [ __ ]<br>[32:40] about Gmail and doesn't bother updating<br>[32:42] it meaningfully is the same reason<br>[32:43] Google's okay with being second place.<br>[32:45] It doesn't matter how much better or<br>[32:47] more private Proton Mail is because<br>[32:49] every company's using [ __ ] Google or<br>[32:51] using Outlook still. I guess it doesn't<br>[32:54] matter that Nano Banana Pro is slightly<br>[32:57] better than GPT image 1.5 because people<br>[33:00] are already using chat GPT. They already<br>[33:02] won. And that's the interesting thing.<br>[33:05] OpenAI does not give a [ __ ] about being<br>[33:07] second place as long as the gap isn't<br>[33:09] that big and they stay first in chat.<br>[33:12] The reason that OpenAI is okay with<br>[33:13] being in second place is because they<br>[33:15] already won first in the only category<br>[33:17] that matters, the app you open when you<br>[33:19] want to talk to an AI. And as long as<br>[33:21] they maintain that lead, they could fall<br>[33:23] the third, fourth, or even fifth place,<br>[33:25] because they're not in this for the<br>[33:27] small wins on benchmarks. They're in<br>[33:30] this to make the most money. And I it<br>[33:32] would be very very surprised if they<br>[33:34] stop making the absurd amounts of money<br>[33:36] they are. OpenAI is going to win even if<br>[33:38] they stay second place. And that's a<br>[33:40] really weird thing to say, especially<br>[33:42] when I'm sitting here wearing my Google<br>[33:44] DeepMind shirt. But yeah, hopefully you<br>[33:47] get the idea. Hopefully this is a useful<br>[33:49] video. Thought it was an interesting<br>[33:50] rant. I'm curious how y'all feel. Let me<br>[33:51] know in the comments. And until next<br>[33:53] time, peace nerds. <!-- deep-read:sections end -->