Google I/O

Google’s 2026 I/O keynote is seen as almost entirely dominated by AI, with Gemini 3.5, agentic workflows, and the Antigravity coding tools drawing both technical interest and fatigue. Commenters praise model quality gains and Google’s massive compute investments, but worry about rising API prices, reliability and quota issues, and AI being awkwardly bolted onto every product while core platforms like Search, Android, and Google Home stagnate. Many express nostalgia for earlier, more diverse I/O events and skepticism about whether current “AI everywhere” strategies are sustainable or really serving users.

Overall Reaction to Google I/O 2026

  • Many commenters say the event felt like “only AI,” with little meaningful focus on Android, hardware, or other traditional product verticals.
  • Some miss earlier I/O eras (Wave, Glass, early Android) and see current keynotes as over-scripted, bland, and marketing-driven.
  • Others argue AI is legitimately transformative and I/O is appropriately AI-heavy, likening this period to the dot-com era.

Gemini 3.5, Flash, and Benchmarks

  • Gemini 3.5 Flash going GA and beating older Pro models on many benchmarks is noted; some are impressed by speed and quality for non-complex tasks.
  • Others question benchmark relevance (e.g., voxel art) and note earlier 3.5 previews struggled with basic code edits.
  • Confusion and debate about whether Flash genuinely outperforms Pro or if evals are poorly aligned with real “agentic” work.

Pricing, Quotas, and Product Strategy

  • Strong frustration over Gemini pricing changes and a perceived “usage rug pull”; some users cancelled paid tiers after rapid quota exhaustion and errors.
  • Concern that Flash 3.5 costs ~3x Flash 3, undermining low-latency, high-volume use cases like support bots and simple RAG.
  • Some see earlier cheap models as loss-leaders; expect prices to rise as subsidies end. Others compare to cheaper VPS-era web hosting and feel gouged.

Antigravity IDE / CLI and Coding Agents

  • Antigravity is widely recognized as a VS Code fork and, in its new form, also resembling other AI desktop apps. Reactions range from “pragmatic reuse” to “uninspired cloning.”
  • Some say it’s better than the old Gemini CLI; others report instability, overload, and poor tool use.
  • Mixed belief in near-term “working coding agents”: some see real promise, others see frequent failures, slop code, and high token costs.

Search, AI Mode, and Ads

  • AI Mode in search is polarizing: some love direct answers and use it intentionally; others find hallucinations dangerous (e.g., made‑up hiking routes).
  • A subset uses AI Mode mainly because ads are less prominent, expecting ads to be reintroduced later.
  • Broader worry that AI-generated “slop” plus ads will further degrade search quality and “kill the open web.”

Agents, Use Cases, and Hype Fatigue

  • Many mock “agentic workflows” and repetitive enterprise jargon (agents, platforms, synergies).
  • Demos like AI-planned neighborhood parties are seen as trivial or socially dystopian.
  • Skeptics say labs are scrambling for real use cases; enthusiasts counter that long-running agents plus massive compute will meaningfully automate “stuff on a computer” and threaten many white-collar roles.

Business Model and Strategic Risk

  • Debate over whether Google will “win the AI race” or destroy its core ad/search business in the process.
  • Concerns about how to monetize LLM answers with ads, and whether incumbents’ AI push simply accelerates user migration to alternative tools or local models.