71–80 of 163 posts
I consider any site that loads 3 seconds to display about 100 bytes worth of unicode text to be utter garbage. I actually wanted to check the precise loading times before posting this, but would you look at this: https://i.imgur.com/VWOlNHu.png I rest my case.
Twitter's website is absolute garbage, the feed is unresponsive, tweets fail to load, it's just terrible. If you're modeling your frontend off of anything please do not pick Twitter because their web experience is awful.
It's not like they have 1000 of concurrent events like facebook, and their frontend should have nowhere the complexity of their backend. I don't understand how it's even happening.
The most absurd aspect of it is that how slow loading a single tweet is. The timeline could have the excuse of a slow and complicated backend call (but it doesn't, the backend is actually doing ok), but several seconds for one single tweet?
Twitter's website is absolute garbage, the feed is unresponsive, tweets fail to load, it's just terrible. If you're modeling your frontend off of anything please do not pick Twitter because their web experience is awful.
It's insane how bad it works on a page that would have been perfectly fine to be simple and static.
I've been searching a stack which could allow for a single codebase to be rendered in Android, iOS, and the web, and React Native + React Native Web might be the top choice for that. Other competitor includes Flutter, which used to only render canvas on the web, but right now it seems they have an option to render as HTML as well. I bet the need for cross-platform stack might continue to rise in the future. It's just…
Earlier quoted context omitted.
I rarely experience any of these issues and think their front end is quite good. Just their a11y / keyboard nav stuff is some of the best I've seen. Some questionable design choices but that's more of a product thing
Tweets not loading, with an error, except after several tries, is a commonly-reported problem. I've seen it for years, across multiple browsers & devices, happens all the time. It might go away if you log in. I wouldn't know.
Earlier quoted context omitted.
I've been encountering this a lot today, because apparently the MTA (and the Metro North) have decided that Twitter is their official news distribution channel [0]. They're posting updates there more frequently than they are on their official website, and because we're in the middle of dealing with a hurricane, they're pushing me to interact with Twitter to figure out how to get home tonight. Apropos of that: the MTA…
Twitter should be a protocol integrated into browsers, not a site.
I consider any site that loads 3 seconds to display about 100 bytes worth of unicode text to be utter garbage. I actually wanted to check the precise loading times before posting this, but would you look at this: https://i.imgur.com/VWOlNHu.png I rest my case.
This is genuinely what I see 50% of the time I go to Twitter. Every other big website can keep their site loading >99% of the time. The fact that Twitter can’t is beyond me, and speaks to their incompetence.
In my mouth, Twitter is probably the best, most responsive web app I've ever used. It is not trivial to make a responsive infinite scroll that remembers your place on back, live updates gracefully, has useful shareable URLs, keeps memory usage low, loads quickly, etc. To me it's the real proof point for RN web and web workers.
Twitter's website is absolute garbage, the feed is unresponsive, tweets fail to load, it's just terrible. If you're modeling your frontend off of anything please do not pick Twitter because their web experience is awful.