Concept

Metaverse

conceptgamingplatform-strategymulti-source
Teach me this →

Metaverse

A large-scale, persistent, multiplayer social space with a shared economy — the term is used by two very different builders in the wiki to mean two different things, and the gap between those definitions is itself the useful takeaway.

Mark Zuckerberg uses ‘metaverse’ to describe a presence problem: hardware and codec technology (Quest headsets, Codec Avatars) that make a digital space feel like being physically together with someone who is not. Tim Sweeney rejects that framing outright — ‘you don’t need VR to have anything like this’ — and defines the metaverse instead as an economic and standards problem: today, players’ friend lists, usernames, and purchased items are locked inside each individual game or platform (Fortnite, Roblox, Xbox, PlayStation, Steam), with no way to carry an identity or a cosmetic item from one to another. On Sweeney’s account, Fortnite Battle Royale already is a metaverse in miniature — a hundred million monthly players, cross-platform voice chat, a $400 million-plus creator economy — precisely because Epic solved that interoperability problem within its own ecosystem, by federating platform friend lists and sharing item-shop revenue according to measured engagement.

What Sweeney says is actually missing

Two layers of standardisation already work, in his account: low-level file formats for 3D data interchange — Pixar’s USD (Universal Scene Description) for scene graphs, and glTF for geometry and textures — let Unreal Engine, Unity, and Blender already exchange static 3D content. What is missing is the equivalent of a web browser’s JavaScript: a programming language capable of running code written by millions of different creators, safely, inside one continuously-updating shared world. Epic’s proposed answer is Verse (see also the Verse section of Tim Sweeney on Unreal Engine, Fortnite, and the App Store Wars), a ‘functional logic’ language whose concurrency model is built to let untrained hobbyist creators write parallel-safe code without manually managing thread conflicts — a harder problem than a webpage, Sweeney argues, because a webpage is one company’s static bundle of code, while a metaverse must be a composite of millions of contributors’ code and content, live-updating without ever shutting down.

The other missing piece is economic rather than technical: an industry standards body — analogous to bodies that already standardise game age ratings or 3D file formats — defining what a ‘portable cosmetic item’ is, so that an outfit purchased in Fortnite could, in principle, work in Roblox or another game, with revenue shared between the originating and hosting ecosystems. Sweeney is explicit that this does not require a new currency: he dismisses both VR and cryptocurrency/NFTs as solutions in search of a problem, arguing ordinary databases or standards bodies — the same mechanism that standardised railroads a century earlier — are sufficient once the technical interoperability exists.

A third account: adoption pacing, not presence or standards

Dave Baszucki, founder of the UGC games platform Roblox, gives the concept a third framing distinct from both Sweeney’s and Zuckerberg’s — not a technical-standards problem and not a hardware-presence problem, but a question of adoption timing. Asked directly whether Zuckerberg’s metaverse vision is dead, Baszucki says no, reaching for a science-fiction analogy: an early film adaptation of Dune depicted something resembling an iPad decades before the device existed, arriving only after several false-start intermediate devices (the PalmPilot, the Apple Newton). His claim is that predicted technologies generally do arrive, just on their own schedule, and that the mechanism of arrival matters more than the fact of prediction.

The specific mechanism he proposes for immersive 3D communication is ergonomic rather than aspirational: people will adopt it not because it is novel or exciting but because, once mature, it will simply be easier than a video call — a superset of video rather than a hype-driven replacement for it. This sits alongside, rather than displaces, the interoperability gap Sweeney identifies and the presence-and-hardware framing Zuckerberg gives the same term; Baszucki’s distinctive contribution is a theory of why now — falling AI token costs are, in his account, the proximate trigger that could finally make that ergonomic threshold reachable, mirroring the same cost collapse already accelerating AI-assisted software development. See Dave Baszucki on Roblox, Teen Entrepreneurs, and the Future of Play.

Where mainstream views differ

The dominant popular association of ‘metaverse’ — reinforced heavily by Meta’s own 2021 rebrand and by Zuckerberg’s own framing on this show — is a VR/AR hardware category: headsets, avatars, and immersive presence as the defining feature. Sweeney’s account directly challenges that framing on two fronts. First, on adoption: he cites 600–800 million people already playing large-scale multiplayer social games monthly, against a comparatively tiny VR user base, as evidence the metaverse (by his definition) is already real and mostly non-VR. Second, on what actually blocks it: he argues the binding constraint is not display technology at all but platform gatekeeping — Apple’s control over what engines and payment systems can run on iOS is, in his account, the single biggest threat to an open, interoperable metaverse ever existing, since a dominant platform could simply mandate its own proprietary metaverse engine the way it already restricts web-app capabilities. See App Store Economics.

In the wiki