Just came here to say: if you're going to beat up on companies and individuals at companies for trying to make things better, we'll end up with a stagnant ecosystem.
-
-
Replying to @davidbrunelle @slightlylate and
Questioning the decisions that were made by the Google Chrome team, as it affects web standards is “beating up on people?!”
1 reply 0 retweets 1 like -
Replying to @AdamRackis @slightlylate and
Alex has offered a pretty thurough explanation of their process and offered to schedule a call with Rich to discuss. What would "good enough" look like?
1 reply 0 retweets 0 likes -
Replying to @davidbrunelle @slightlylate and
Achieving consensus with other browsers before shipping things (as stable) to the most dominant browser in the world. Why more people aren’t pissed that Chrome is abusing their market power to push their pet projects into the web platform is beyond me.
1 reply 0 retweets 3 likes -
Replying to @AdamRackis @slightlylate and
Have you ever tried to drive consensus amongst a group of people? Try doing the same thing with a group of for-profit companies with competing goals. Waiting for complete "consensus" is how momentum stops.
3 replies 0 retweets 3 likes -
Replying to @davidbrunelle @AdamRackis and
The Chrome team has been the driving force behind many of the capabilities that allow me to build better web apps. If we waited for Safari to lead the way (or catch up), what would that look like?
2 replies 0 retweets 0 likes -
Replying to @davidbrunelle @slightlylate and
SW come to mind. You may be thinking of others. Was iDB Google’s doing? Props if so I’d be curious if Google pushed headlong with any of them even after other implementors called out “showstoppers” on very real problems (race condition on mundane async code to add a stylesheet!)
1 reply 0 retweets 0 likes -
Replying to @AdamRackis @davidbrunelle and
The "race condition" term here is misleading. It belies a misunderstanding of the event loop or scopes, hard to tell from the thread. Neither is a good look in debates about style application.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @davidbrunelle and
Adam Rackis Retweeted Rich Harris
Subtle race conditions affecting which stylesheet is applied in which order absolutely exist, but really are the least of the problems with this api. https://twitter.com/rich_harris/status/1220479580298977281?s=21 …https://twitter.com/Rich_Harris/status/1220479580298977281 …
Adam Rackis added,
Rich HarrisVerified account @Rich_HarrisReplying to @BurialOfTheDeadasync function add_this_stylesheet(href) { document.aSS = [...document.aSS, await import(href)]; } add_this_stylesheet('./foo.css'); add_this_stylesheet('./bar.css'); Whichever stylesheet comes over the network first will get blown away by the second one1 reply 0 retweets 0 likes -
Replying to @AdamRackis @davidbrunelle and
Input on compatible improvements is greatly appreciated. It's how progress gets made on platforms. Arguing about how this is illegitimate because it isn't yet perfect is
, particularly when "fix" is trivial.3 replies 0 retweets 0 likes
First, not growing how promises work is how you get bugs w/ promises code. Second, we *can* add methods! So which ones do you want?
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.