# Ecosystem Gravity Retains Developers Better Than Feature Parity ## Claim A language or platform retains its developers primarily through the depth and availability of its surrounding ecosystem — libraries, tools, and community answers already existing for whatever comes up — not through matching the specific language features that competing platforms happen to have. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds for mature platforms with an already-large ecosystem, where the marginal value of a new language feature is small relative to the marginal value of "someone already built this." - The claim is about retention, not adoption — a newcomer choosing between platforms for the first time may weigh language features more heavily than an established practitioner deciding whether to stay. - Breaks where the missing feature blocks something the ecosystem genuinely can't route around (a fundamental capability gap, not a convenience gap) — ecosystem depth can't substitute for a hard technical ceiling. - Weakens as a competing platform's ecosystem matures — the claim describes a durable but not permanent advantage; ecosystems can be built. ## Evidence A PHP Architect podcast host's Swift/Vapor comparison: "I can write swift on the server using Vapor and a handful of other tools, but you know what? I don't have the ecosystem." The illustrating anecdote is small and concrete — told on Mastodon that code on their blog wasn't readable, the answer arrived as an existing PHP library (Tempest) within minutes. The claim generalizes the observation that PHP's longevity (people still running PHP 5 in production) is itself evidence of ecosystem adequacy, and that the recurring "PHP needs feature X because other languages have it" argument misdiagnoses what actually keeps developers from leaving. > [!quote] > I can write swift on the server using Vapor and a handful of other tools, but you know what? I don't have the ecosystem. ## Links - [[3. Resources/Permanent Notes/Open-Source Design Tools Reach Parity Through Community-Contribution Velocity]] — because contrasts; that note is about how a young ecosystem catches up to an incumbent through contribution velocity, this note is about why an incumbent's already-built ecosystem is hard to dislodge even when a competitor has comparable core language capability. - [[3. Resources/Permanent Notes/Maintainer Attention Is the Scarce Resource in Open Source]] — because applies-in; ecosystem depth is downstream of accumulated maintainer attention over time, which is exactly the scarce resource that a newer platform can't buy quickly. - [[3. Resources/MOCs/Open Source Governance MOC]] — because applies-in; platform-retention dynamics for open-source language communities. ## Tests / falsifiers - Survey developers who left a mature platform for a newer one with comparable ecosystem depth — if feature gaps, not ecosystem gaps, are the dominant stated reason, the claim is wrong about what actually drives departure. - Track whether a platform that closes its feature gap with competitors (without ecosystem changes) shows measurably reduced attrition — if feature parity alone moves retention, ecosystem gravity is doing less work than claimed. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/The PHP Podcast 2026.07.30]] — the Swift/Vapor comparison and the Tempest-library anecdote.