The Web Is More Than Enough

Whether the web is now “enough” as a universal application platform provokes sharp disagreement: some see modern browsers, PWAs, and powerful APIs as a secure, ubiquitous sandbox that already replaces most native software, while others argue web apps remain bloated, inconsistent, and inferior to well-designed desktop or mobile programs. Commenters debate developer freedom versus platform control, contrasting open standards and browser-based distribution with app store gatekeeping, OS-level sandboxes, and tightening restrictions on native binaries. AI enters the picture as both a force making complex web (and native) development easier and a source of low-quality “slop,” raising questions about code ownership, job security, and the long‑term shape of software ecosystems.

Web as Application Platform

  • Many argue the web is already the primary app platform: email, docs, chat, collaboration, mapping, and many business tools all run in browsers.
  • Others feel we’re “further from ‘web is enough’ than 5 years ago,” citing areas like games, heavy graphics, and developer tooling where native still dominates.

Native Apps vs Web Apps

  • Pro‑web side: prefers browser sandboxing, easy distribution via URLs, cross‑device reach, tabs/bookmarks, and user scripting/extension-based customization.
  • Pro‑native side: emphasizes performance, tighter hardware integration, better UX for complex tasks, and less dependency on heavyweight browsers and JavaScript.
  • Some blend both views: web is ideal for UIs and broad reach; native stays superior for hardware‑heavy use cases (AAA games, AR/VR) and offline/local workflows.

Security, Sandboxing, and Privacy

  • Browsers seen as strong sandboxes versus traditional desktop apps that can access files, camera, mic, etc.
  • Counterpoint: web APIs (e.g., WebUSB, WebRTC) and tracking make browsers powerful but also attack surfaces; security benefits are partly offset by pervasive surveillance and vulnerabilities.

App Stores, Platform Control, and User Freedom

  • Strong criticism of iOS and Play Store gatekeeping, fees, review delays, and policy unpredictability.
  • Some note sideloading and alternative OSes (Linux, *BSD, AOSP derivatives) as escape hatches, but these are seen as niche and increasingly encumbered by signing/security requirements.
  • Web is framed by some as the last “permissionless” mass platform; others argue browser monoculture (Chromium/WebKit) is itself a centralization risk.

Browser Engines, Standards, and Power

  • Debate over who “controls” the web: some point to W3C/WHATWG and multi‑stakeholder governance; others highlight de facto dominance by Google’s Chromium.
  • Concern that implementing a modern browser from scratch is prohibitively complex, limiting diversity, though new projects (e.g., Ladybird) are noted.

AI’s Role in Web Development

  • Multiple anecdotes of LLMs rapidly producing sophisticated WebGL/3D demos and ports (e.g., Three.js → vanilla WebGL), making advanced browser features more accessible.
  • Discussion over whether saying “I built this” is accurate when AI generates much of the code; some frame it as a team‑like collaboration, others as tool use akin to compilers/IDEs.

Complexity, Performance, and Nostalgia

  • Complaints that modern web stacks are bloated and harder than older tools like Visual Basic; web layout/responsiveness and JS ecosystem are seen as overcomplicated.
  • Some nostalgia for the simpler, document‑centric web of ~1998–2005, arguing many problems (tracking, fingerprinting, heavy pages) stem from overextending the browser.