How Web Standards Work 1. design a flawed API (it's fine! APIs are hard) 2. ship it in the most-used browser, despite objections 3. get cross-browser working group to fix the API 4. oops, too late, that would break the webpic.twitter.com/IuU6Xxzilv
Chrome Project
& Web Standards TL; Blink API OWNER
Named PWAs w/ @phae; probably making her
DMs open. Tweets my own; press@google.com for official comms.
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
How Web Standards Work 1. design a flawed API (it's fine! APIs are hard) 2. ship it in the most-used browser, despite objections 3. get cross-browser working group to fix the API 4. oops, too late, that would break the webpic.twitter.com/IuU6Xxzilv
Hi Rich, I run standards for Chrome. If you'd like to discuss our approach, happy to set up a call.
Would it result in changes to how you do things, so that web developers are spared further episodes like this one?
Serious question: Why would this change “break the web” ? Constructable stylesheets are behind a flag, since they’re non-standard, right? Why can’t they be changed at this point? There’s never an expectation of stability when stuff is behind a flag, right?
They're shipped to stable Chrome (and many Chromium embedders enable them too).
As the person who runs standards for Chrome, can you please explain how the fuck a non-standard feature got shipped to Stable Chrome?
We often lead, balancing risk/reward rather than demanding a particular point in an arbitrary process. https://www.chromium.org/blink/launching-features … Leadership is rather the point of having an engine team, after all.
Given that chrome has a near monopoly don't you think you should maybe not ship something as stable before other browsers have it to not reinforce the monopoly?
FWIW this is how the web has ALWAYS evolved. Almost all APIs we use today we're shipped in the dominant engine prior to a standard being ratified (IE, Netscape, WebKit, now chromium). JavaScript language is a notable and impressive counter-example.
It isn't, tho. NN 2 unilaterally added livescript. MSFT copied and forced standardisation at ECMA. Same as it ever was.
Surely Rick meant modern JS, ie ES6 and beyond, when he noted how impressive the JS standardization was? I've sadly not been in web dev long enough (originally a boring, corporate .net dev) to even know what you're referring to -- LiveScript? Did you just make that up? ;)
Modern JS evolution has been a disaster -- and I say that as someone who has pushed the boulder up the hill as much as anyone. We introduced the stages model after some of the worst, but still not on productive footing.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.