61–70 of 163 posts
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.
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
You literally can't use the site properly when you're not logged in (and I mean basic clicking on retweeted/quoted stuff shows a login page, clicking on people's names shows a login page etc.) - how is that good? (I mean sure, build your walled garden as you please, but then you have no business showing in search engine results.)
Apropos of that: the MTA is using threads now, and I can't click 'show thread' without being redirected to a login screen. I don't want to create an account because I find twitter painfully shallow but also addictive, as well as generally untrustworthy (I don't want them to have my phone number).
I don't think that any part of the government should be using twitter the way the MTA is; but so long as they are, I think Twitter would do well to get out of the way of the distribution of vital info.
Earlier quoted context omitted.
I mean... I'm perfectly fine hitting buttons to goto the next page honestly.
I kinda want to agree but then, I practically never do hit that button. Not on google search results. Not on hacker news.
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.
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.
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
It might go away if you log in. I wouldn't know.
Earlier quoted context omitted.
You literally can't use the site properly when you're not logged in (and I mean basic clicking on retweeted/quoted stuff shows a login page, clicking on people's names shows a login page etc.) - how is that good? (I mean sure, build your walled garden as you please, but then you have no business showing in search engine results.)
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…
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…
I'm a solo developer, and I have a project that totally can do it. I've done the proof-of-concept in an afternoon, but am mostly focused on web stuff atm. Granted, it leverages NativeScript, but it's really not that hard once you have that.
To the eyes of someone familiar with the framework it is still full of bad practices.
So pardon my ignorance but I thought React was already for web and React Native merely a set of tools to help port React web apps to native mobile apps. What is the difference between React for web and React Native for web?
An important distinction that often gets lost is that React itself is an abstract, standalone layer above web and native. It handles deciding what to render and when. When you learn the concepts of React, you're learning this layer. Then there are layers that decide how to render. Regular React has a renderer that accepts HTML tags spits out HTML for the browser. React Native has a renderer that accepts more abstract…
To be followed by "React Native for the Web for Native for the Web" to port those apps back to the Web..
At some point they will just emulate a browser into a PC into a browser to make your code more portable
