This is how it spreads. Google normalizes “web apps” that are really just Chrome apps. Then others follow. We’ve been here before, y’all. Remember IE? Browser hegemony is not a happy place.https://twitter.com/yaroslav/status/1112707497083785216 …
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.
DHH Retweeted Yaroslav Markin
This is how it spreads. Google normalizes “web apps” that are really just Chrome apps. Then others follow. We’ve been here before, y’all. Remember IE? Browser hegemony is not a happy place.https://twitter.com/yaroslav/status/1112707497083785216 …
DHH added,
In fact, it’s alarming how much of Microsoft’s cut-off-the-air-supply playbook on browser dominance that Google is emulating. From browser-specific apps to embrace-n-extend AMP “standards”. It’s sad, but sadder still is when others follow suit.
It seems to me that what’s really going on is developers are choosing to punt on support and testing for less dominant browsers while taking advantage of the latest (standards based) features in Chrome. @slightlylate may have stronger rhetoric. Doesn’t feel like IE6 to me.
Hey all; friendly Chrome engineer here. I'm one of the people who is both pushing Google teams to broaden their browser support as well as one of the people who is pushing the platform to expand its capabilities. The situation isn't binary.
The big dissonance (from my perspective) is that the web "won" desktop but has failed (to date) on mobile. Other engines aren't focused on the latter, and are generally under-investing. This grows the distance between engines. See also: https://web-confluence.appspot.com/#!/confluence
We're investing heavily in Web Platform Tests to make it easier for lagging engines to catch up: https://wpt.fyi But no amount of cowpath-paving can address other engines fundamentally under-investing, and that's the situation we're in.
And WRT to IE6, I think we can investigate the history with a bit of distance. I was a web developer at the time (and for many years after), and the common story about what went wrong in that era is...missing nuance.
IE6 was hands down, flat-out, the single best browser available when it was released, which followed IE 4, 5, and 5.5 which were the best browsers when *they* were released. By a long shot. IE6 enabled the Ajax world we all worked hard to build out. Its sins lay elsewhere.
...primarily that MSFT disbanded the team at some point in the early '00s. All the bad stuff we were exposed to by IE6 was, at some level, a consequence of MSFT divesting itself of the web and failing to replace IE6 with something better at the same pace IE 4, 5, and 5.5 were.
So if you want to trot out the rhetorical "new IE6", maybe we can point that critique at engines that are under-invested and don't allow for real competition...say...Safari for iOS?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.