Post #4235859
2026-07-30 08:53 UTC
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.
Replies (1)
-
@Girgias@phpc.social 2026-07-30 09:41
@slightlyoff@toot.cafe stuff being in limbo is always bad :/ I feel the main reason why something ends in limbo for us is just the single author/implemented lost the drive (or maybe that's just me who knows). I do think being able to "fail" quickly is good, but the current mood in PHP Internals is that the vote should effectively be a formality. Which is very hard to determine considering the very large, mainly inactive, voting pool that exists.