Hacker News Reader

Comment by TekMol | Hacker News Reader

    mobile.twitter.com

I really don't like it. It's one of these typical slow react experiences where everything I do results in me staring at a loading animation.

For example the search experience: I type something and before the typeaheads show up there is a loding bar on top of them. And when I hit enter, I get a loading spinner in the center of the screen.

Another example: When I click on a tweet and then click the back button. The page where I came from could be shown instantly. Instead I get some type of fade-in effect on some elements.

Etc etc. The whole experience feels terrible clunky on mobile.twitter.com.

Compare that to Googles search for example, where everything feels instant. Typeaheads, result pages ... when I click through to a result and hit the back button - I'm instantly at the same result page where I was before.

View on HN

> these typical slow react experiences

Again, this is a really bad generalisation you're making. It is ludicrous to attribute the types of slowness you're talking about to React.

> Compare that to Googles search for example

Do you think it's fair to compare anyone's search to Google's?

Well, sorry but you're wrong about React. You haven't shown any evidence that these things are related to React at all.

Here's some counter-evidence though - https://reactjs.org - that site is built with React and everything is instant.

Also, my own React apps perform instantly and that's because I didn't put in a shitload of JS to do things like track your mouse pointer and do other types of analytics like Twitter probably does.

    reactjs.org

When I visit it, the lower half of the screen makes a jump to the left after about 3 seconds. That already makes me feel uneasy.

In the 'Tutorial' section, everytime I click on an entry on the right, the screen at first jumps up for a fraction of a second before jumping down again.

Sounds like there might be something seriously wrong with your computer, your device, network or your browser then. What’s your set up?

I just looked at it on like four different devices and didn’t have any problem. It works perfectly for me on Windows 10 with Chrome, Mac High Sierra/Chrome and iOS 11 / Safari iPad and iPhone.

If you don’t believe me, I will post a screen cast on imgur if you’d like.

Yup, screen cast please.

You can see the jumping on webpagetest.org:

https://www.webpagetest.org/video/compare.php?tests=180616_B...

With a slow connection, on the initial load the first jump happens at 6s and another one at 8.5s.

When I click on one of the links, it happens much faster because everything is cached. But I can still see the jump everytime I click a link to a new section in the tutorial.

I don't think the type of browser plays a role here. I get the glitches on Chrome and Firefox. And testing it on browserling.com shows that they also happen on Internet Explorer.

The jump is the anchor '#how-to-follow-along'. A mechanism that's existed since the beginning of the internet. https://www.w3.org/MarkUp/1995-archive/Elements/A.html ‍️

Anchors by themselves do not make browsers jump in erratic ways. Try Wikipedia. No glitches when you click on sections.

Here it is on my iPhone, arguably the slowest device that I tried it on - https://imgur.com/a/Wf2bXmq

Not really counterevidence, they use gatsby to create static sites from react code, it is not a PWA

Reply on news.ycombinator.com