Steam Client is now faster than Epic's new vibe coded launcher

Original Article ↗ Hacker News Discussion ↗

Epic’s boast that its new AI‑assisted “vibe coded” game launcher starts faster than Steam prompted users to benchmark both clients and question whether a few seconds of startup time really matters. Many argue that competition is positive if it forces Valve to optimize a long‑criticized, Chromium‑based client, but note that both launchers remain bloated, slow to start on some systems, and missing opportunities to reduce RAM usage or avoid always‑running background processes. Beyond performance, commenters contrast Steam’s richer ecosystem and Linux support with Epic’s more bare‑bones, tightly controlled platform, while expressing unease about marketing AI as a replacement for traditional engineering.

Performance and UX of Steam vs Epic

  • Many users report Steam still takes 7–15s on cold start and ~0.5–2s to restore, with Epic often somewhat faster; others say startup time is irrelevant because they leave clients running.
  • Some find Steam especially sluggish on macOS and avoid the client store, preferring a browser. Others say it’s acceptable relative to game load times and bandwidth-heavy tasks.
  • Focus stealing and UI jank (blank pages, slow video playback, two different menu bars, multi‑monitor glitches) are recurring complaints; the recent change to reduce focus stealing is welcomed.
  • Memory usage and background processes are major pain points, especially on laptops. Some users quit Steam to reclaim RAM; others see ~100MB idle and don’t care.

Competition and Platform Features

  • Several argue competition from Epic likely nudged Valve to ship existing optimizations faster; others note the Steam beta with speedups predates Epic’s boast.
  • Steam is praised for: Linux/Proton investments, Steam Deck/VR ecosystem, community hubs and guides, sales, cloud saves, controller mapping, multi-location installs, and generally stable libraries.
  • Epic is criticized for: missing reviews and community features, deliberate avoidance of user feedback mechanisms, account/security annoyances, region restrictions, and past exclusivity deals.
  • Some see strong “platform loyalty” to Steam and note parasocial, console‑war‑style behavior; others defend Valve as comparatively consumer‑friendly and one of the few champions of Linux gaming.

AI and “Vibe Coding”

  • “Vibe coding” is seen by many as marketing spin that trivializes actual engineering work and risks normalizing sloppy outputs.
  • Several assume both Steam and Epic engineers quietly use LLMs; some describe good results using AI for code optimization and refactoring.
  • Others worry AI‑authored code drives “broken windows” and lower quality standards, though they concede optimization is a strong use case.

Tech Stack, Bloat, and Alternatives

  • Steam uses CEF/Chromium; Epic’s new launcher uses Tauri/WebView2. Debate centers on disk size vs RAM vs reliability of system webviews.
  • Many lament “everything is a browser now,” blaming Electron‑style stacks for multi‑GB launchers and slow starts; some advocate native Rust/GPUI, Tauri, or other lightweight toolkits.
  • A minority argue web tech is a pragmatic cross‑platform choice given real‑world constraints and existing developer skill pools.

Article and Metrics Skepticism

  • Multiple comments call the linked article low quality: no same‑machine comparison, no before/after for Steam, cherry‑picked clips, and confusing or misleading tables.
  • Users emphasize that startup metrics depend on configuration (store vs library start page, pop‑ups, beta vs stable) and network conditions; claims of universal timings are labeled “nonsensical.”

Broader Reflections

  • Many see launcher performance wars as a symptom of broadly low performance standards and tolerance for bloat.
  • Others nostalgically note that games once ran without any launcher, and wish modern stores offered minimalist, native, fast clients.