Thankfully it gives you this helpful error message so that you don't try to load it on a mobile device:pic.twitter.com/3oilwynF2Z
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.
Thankfully it gives you this helpful error message so that you don't try to load it on a mobile device:pic.twitter.com/3oilwynF2Z
I'm a glutton for punishment tho, so let's trace this on a Moto G4 just so we can see what "modern" webdev hath wrought, shall we?
This: https://chromedevtools.github.io/timeline-viewer/?loadTimelineFromURL=https://dl.dropboxusercontent.com/u/6792555/riot/moto_G4_emulated_3g_TimelineRawData-20161021T105745 … This is what "modern" webdev looks like, and it's so full of fail I can't even.
^^^ is not OK, not even a little bit. It wouldn't even be OK on wifi. This is what taking control but not responsibility looks like.
And make no mistake: when you write JavaScript and make your app depend on it, you are taking control away from the browser. You OWN it.
...so if you break it (the way Riot has), there's nobody else to blame.
This is what I mean about not being able to afford the JS we include. Nobody marked this to market (how it performs on a real device).
So if this looks like your app -- a giant pile of JS -- and you think "server rendering" will get you out of jail, step away from the kbd.
These architectures harm users. They harm the web. They are not acceptable. Less JS, loaded better, is what we need now.
Do you think it’s time to bid farewell to polyfill it all away? Perhaps we must look at what can be stripped back out
: I think setting realistic budgets will illuminate these tradeoffs
Was just pondering that - has there been anything written about what are good budgets for different devices/connections?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.