Post

Mary Branscombe
@marypcbuk.bsky.social

Also, having just spent more hours than it ought to take looking up discussion minutes for stage 4 tc39 proposals, better information linking and indexing might move things along or just make them more consumable.

Mary Branscombe
@marypcbuk.bsky.social

Intl locale variants proposal had an index list of slides and discussions for every stage which was brilliant, digging into the evolution and final shape of json.propose source text meant repeated manual searches on GitHub to find the same info

Michael Champion
@abunadh.bsky.social

"Still, every year a huge number of things remain in the pool that we can’t afford to take up. The pool keeps growing." That seems be the root of the problem. Nothing kills off "not quite good enough" ideas.

Brian Kardell
@bkardell.com

Its hard to say that's all of it. Sometimes the ideas just need refinement too, or they could look better after a lot of time. Grid had a few false starts, container queries absolutely weren't going to happen, nor :had

Michael Champion
@abunadh.bsky.social

Well, "triage" means classifying ideas that are ready to be implemented, promising ones that need work, and those that aren't worth / ready for a lot of work. It's hard, and mistakes happen. But if you let things just muddle along until the choice is obvious, you get the current situation 🤷‍♂️

Michael Champion
@abunadh.bsky.social

"Good enough" ideas have a high threshold because "yes" means "we have to support it forever". For example client-side XSLT seemed like a great idea 25 years ago, but now it doesn't have enough users attract maintenance resources, but enough to make it difficult to remove. No-win scenario.

Michael Champion
@abunadh.bsky.social

In a single org, there might be Product Managers that triage out not-quite-good-enough ideas, but the web platform doesn't have a Project Management team. I've heard arguments that the TAG/ should evolve into one, but that idea isn't quite good enough to get traction either