Post #4235860
2026-07-30 08:53 UTC
@Girgias@phpc.social We introduced the Stages process after the lurching, exhausting experience of ES6, which only got over the line because some of us pushed *very* hard to finally bloody ship.
At that point there was appetite in the room to entertain better processes, and Stages were a solution we (the Web Platform side of the Chrome team, not the V8 side) introduced. Things have gone roughly as I predicted it would, owing to explosion of veto players: some small stuff, very little big stuff, all overdue
Replies (1)
-
@slightlyoff@toot.cafe 2026-07-30 08:53
Contrast that with WICG at W3C where we have many proposals that fail (which is good!) and some which ship at the speed of interest. TC39 has many proposals that sit in limbo ~forever. Always takes implementer interest to move something on the web, but when that spark catches, process shouldn't extinguish it with overwhelming reliability. Goal should be to nurture, find community, and get things going through coalitions of the willing.