One-pager layout and copy refinements · burrito.space/servo-readiness-report@11c065d

+1 -1

dashboard.html

··· 49 49 <h1>Servo Baseline Readiness</h1> 50 50 <div class="byline">Dietrich Ayala — dietrich@webtransitions.org — <a href="https://webtransitions.org">webtransitions.org</a></div> 51 51 <div style="background:rgba(71,11,0,0.04);border:1px solid rgba(71,11,0,0.15);border-radius:8px;padding:14px 18px;margin-bottom:16px;font-size:14px;line-height:1.5;color:#1d1d1d;"> 52 - Servo is falling behind the web. It completes ~22 features/year at production quality, while the Baseline “<a href="https://web-platform-dx.github.io/web-features/" target="_blank">Widely Available</a>” set grows at ~52 features/year. At this pace, Servo plateaus around 80% by ~2037 and never catches up. Full velocity parity requires ~44 FTE (€8.8M/yr, €26.3M over 3yr). BWA features vary widely in real-world usage — a phased approach that prioritizes high-usage features first could reduce the initial headcount and cost by up to 40% while building toward full parity. The highest-leverage actions are unstalling 141 blocked features and fixing 51 regressions (features that lost >5 percentage points). This report asks: what would it cost in engineering investment alone to bring Servo to velocity parity within 3 years, excluding non-engineering and operational costs? 52 + Servo is falling behind the web. It completes ~22 features/year at production quality, while the Baseline “<a href="https://web-platform-dx.github.io/web-features/" target="_blank">Widely Available</a>” set grows at ~52 features/year. At this pace, Servo plateaus around 80% by ~2037 and never catches up. Full velocity parity requires ~44 FTE (€8.8M/yr, €26.3M over 3yr). BWA features vary widely in real-world usage — a phased approach that prioritizes high-usage features first could reduce the initial headcount and cost by up to 40% while building toward full parity. The highest-leverage actions are unstalling 141 blocked features and fixing 51 regressions (features that lost >5 percentage points). This is a work-in-progress analysis focusing on one aspect of web engine development — feature-level readiness — and is not exhaustive. It is designed to orient thinking about cost and timelines. The central question: what would it cost in engineering investment alone to bring Servo to velocity parity within 3 years, excluding non-engineering and operational costs? 53 53 </div> 54 54 55 55 <div class="metric">

+14 -17

data/build-one-pager.mjs

·················· 312 309 Readiness measured against Baseline “Widely Available” (BWA) web features — supported 30+ months across all major browsers. Feature scores from Web Platform Tests (WPT) via WPT Feature Manifest mapping. ${measurableCount} of ${totalBWA} BWA features are measurable; ${noDataCount} lack WPT mapping (${(noDataByReason['js-builtin'] || []).length} JS built-ins tested by test262 not WPT, ${(noDataByReason['semantic-html'] || []).length} semantic HTML elements, ${noDataCount - (noDataByReason['js-builtin'] || []).length - (noDataByReason['semantic-html'] || []).length} other with unknown status). FTE-equivalent from per-author commit frequency (1 FTE ≈ 22 commits/month, capped at 1.0 per person; 115 authors sum to ~${currentContributors} FTE). BWA growth rate of ~${bwaGrowthPerYear}/year is the 2023–2025 average, normalized to exclude the 2022 interop spike. Known pipeline: ${projectedBWA.filter(p => p.year <= 2028).reduce((s, p) => s + p.added, 0)} features graduating by 2028. Velocity parity = Servo’s annual feature completion rate ≥ BWA annual growth rate. Completions/yr = ${servoCompletionsPerYear} × (FTE/${currentContributors})${SCALING_EXP} (sublinear <a href="https://en.wikipedia.org/wiki/Brooks%27s_law">Brooks’s Law</a> scaling). Stalled = zero or negative velocity over the full observation period (2023-Q3 to 2026-Q1). Regressions = features that lost >5 percentage points. Cost at €${(SALARY/1000).toFixed(0)}k/yr per FTE: €${(BASE_SALARY/1000).toFixed(0)}k European senior SWE median total cost × ${SPECIALIZATION_MULTIPLIER}× premium for browser-engine specialization (small talent pool, Rust/rendering/layout) and multi-disciplinary practice (software development + W3C/WHATWG standards participation + open-source community management). Calibrated against <a href="https://nlnet.nl/core/faq/">NLnet</a> (€117k, up to €65/hr), <a href="https://www.sovereign.tech/programs/fellowship">Sovereign Tech Fund</a> (€79–101k, TVöD-Bund + employer costs), <a href="https://www.levels.fyi/companies/mozilla/salaries/software-engineer/locations/germany">Mozilla Germany</a> (€145–164k), and <a href="https://github.com/servo/project">Servo grant rates</a> (€248k US contractor). Excludes other opex, infrastructure, management overhead, and inflation. Usage-prioritized scenarios: at <1% threshold, ${drop1_count} features deprioritized (target ${target_drop1}, growth ~49/yr); at <5%, ${drop5_count} features deprioritized (target ${target_drop5}, growth ~47/yr). Data: wpt.fyi, web-features, Servo git history. Full interactive dashboard: dashboard.html.

+1 -1

data/generate-dashboard.mjs

··· 237 237 <h1>Servo Baseline Readiness</h1> 238 238 <div class="byline">Dietrich Ayala — dietrich@webtransitions.org — <a href="https://webtransitions.org">webtransitions.org</a></div> 239 239 <div style="background:rgba(71,11,0,0.04);border:1px solid rgba(71,11,0,0.15);border-radius:8px;padding:14px 18px;margin-bottom:16px;font-size:14px;line-height:1.5;color:#1d1d1d;"> 240 - Servo is falling behind the web. It completes ~${servoCompletionsPerYear} features/year at production quality, while the Baseline “<a href="https://web-platform-dx.github.io/web-features/" target="_blank">Widely Available</a>” set grows at ~${bwaGrowthPerYear} features/year. At this pace, Servo plateaus around ${ceilingPct}% by ~${ceilingYear} and never catches up. Full velocity parity requires ~${parityFTE} FTE (€${parityCostPerYear}M/yr, €${parityCost3yr}M over 3yr). BWA features vary widely in real-world usage — a phased approach that prioritizes high-usage features first could reduce the initial headcount and cost by up to 40% while building toward full parity. The highest-leverage actions are unstalling ${stalledFeatures.length} blocked features and fixing ${regressions.length} regressions (features that lost >5 percentage points). This report asks: what would it cost in engineering investment alone to bring Servo to velocity parity within 3 years, excluding non-engineering and operational costs? 240 + Servo is falling behind the web. It completes ~${servoCompletionsPerYear} features/year at production quality, while the Baseline “<a href="https://web-platform-dx.github.io/web-features/" target="_blank">Widely Available</a>” set grows at ~${bwaGrowthPerYear} features/year. At this pace, Servo plateaus around ${ceilingPct}% by ~${ceilingYear} and never catches up. Full velocity parity requires ~${parityFTE} FTE (€${parityCostPerYear}M/yr, €${parityCost3yr}M over 3yr). BWA features vary widely in real-world usage — a phased approach that prioritizes high-usage features first could reduce the initial headcount and cost by up to 40% while building toward full parity. The highest-leverage actions are unstalling ${stalledFeatures.length} blocked features and fixing ${regressions.length} regressions (features that lost >5 percentage points). This is a work-in-progress analysis focusing on one aspect of web engine development — feature-level readiness — and is not exhaustive. It is designed to orient thinking about cost and timelines. The central question: what would it cost in engineering investment alone to bring Servo to velocity parity within 3 years, excluding non-engineering and operational costs? 241 241 </div> 242 242 243 243 <div class="metric">

+14 -17

one-pager.html

·················· 195 192 Readiness measured against Baseline “Widely Available” (BWA) web features — supported 30+ months across all major browsers. Feature scores from Web Platform Tests (WPT) via WPT Feature Manifest mapping. 439 of 593 BWA features are measurable; 154 lack WPT mapping (78 JS built-ins tested by test262 not WPT, 23 semantic HTML elements, 53 other with unknown status). FTE-equivalent from per-author commit frequency (1 FTE ≈ 22 commits/month, capped at 1.0 per person; 115 authors sum to ~13 FTE). BWA growth rate of ~52/year is the 2023–2025 average, normalized to exclude the 2022 interop spike. Known pipeline: 130 features graduating by 2028. Velocity parity = Servo’s annual feature completion rate ≥ BWA annual growth rate. Completions/yr = 22 × (FTE/13)0.7 (sublinear <a href="https://en.wikipedia.org/wiki/Brooks%27s_law">Brooks’s Law</a> scaling). Stalled = zero or negative velocity over the full observation period (2023-Q3 to 2026-Q1). Regressions = features that lost >5 percentage points. Cost at €200k/yr per FTE: €150k European senior SWE median total cost × 1.33× premium for browser-engine specialization (small talent pool, Rust/rendering/layout) and multi-disciplinary practice (software development + W3C/WHATWG standards participation + open-source community management). Calibrated against <a href="https://nlnet.nl/core/faq/">NLnet</a> (€117k, up to €65/hr), <a href="https://www.sovereign.tech/programs/fellowship">Sovereign Tech Fund</a> (€79–101k, TVöD-Bund + employer costs), <a href="https://www.levels.fyi/companies/mozilla/salaries/software-engineer/locations/germany">Mozilla Germany</a> (€145–164k), and <a href="https://github.com/servo/project">Servo grant rates</a> (€248k US contractor). Excludes other opex, infrastructure, management overhead, and inflation. Usage-prioritized scenarios: at <1% threshold, 35 features deprioritized (target 558, growth ~49/yr); at <5%, 56 features deprioritized (target 537, growth ~47/yr). Data: wpt.fyi, web-features, Servo git history. Full interactive dashboard: dashboard.html.

Configure Feed

Configure Feed