For my part, I want frameworks to be involved and driving the discussion in a multi-lateral way, but it seems difficult to activate interest. Bi-lateral design seems destined to result in benefits for incumbents.
-
-
TC39 has been having amazing framework meetings for ages now (thanks
@littledan !) The TC39 champion process allows framework devs to work with implementors on designs, and the meetings produce regular reality checks for the designs.1 reply 0 retweets 4 likes -
The key is treating framework authors as true blue partners, not just people to get periodic feedback from (because feedback that comes after a lot of design investment is likely to be met with skepticism, and require framework devs to meet a high bar for even minor changes).
1 reply 0 retweets 3 likes -
The process that led to Display Locking wasn't perfect, but much much better.
1 reply 0 retweets 0 likes -
It sounds amazing. I have no idea how we go from where we are today to what you just described.
2 replies 0 retweets 0 likes -
It would be nice if someone with more authority on this topic could lay out a vision that the rest of us could start advocating for...
1 reply 0 retweets 0 likes -
It is also real life in TC39. It's not perfect but it's better. It would be useful if everyone on the Chrome team abandoned the assumption that framework participation in TC39 slows things down and therefore TC39 is a toxic place to work.
1 reply 0 retweets 0 likes -
Before someone pops up and "lol"s what I'm saying about TC39, I am *not* saying that TC39 is a perfect standards body with no slowdowns caused by committee failure modes. I *am* saying that its normal working mode (in 2019), respects proposals championed by framework devs.
3 replies 0 retweets 1 like -
I'm also saying that the framework outreach group (started by
@littledan) has effectively gotten feedback and prioritization by a larger group of framework devs, and that busy people have found it valuable enough to keep showing up.1 reply 0 retweets 4 likes -
All of this in the service of arguing that if we put together a task force to make web components useful for frameworks, and focused its energy on things we could do quickly, I think we would make some progress pretty fast. Some recent features modelled this so I'm optimistic.
2 replies 0 retweets 6 likes
This is a vile misrepresentation of the history and practice of the Chrome team and you know it. Stop.
-
-
Replying to @slightlylate @0xcda7a and
I try my best to be honest about my own recollections. Not intending to misrepresent, vile or otherwise. You should consider the relative power dynamics here and try a different approach than "shut up"
0 replies 0 retweets 3 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.