On: The Performance Cost of Server Side Rendered React on Node.js

[qaq]

did you ever consider that you might not be doing something right ?

[dustingetz → qaq]

Not really, I'm the consultant people hire when they need to solve issues like this. There are some screenshots of what we're doing here: http://www.hyperfiddle-consulting.com/ http://hyperfiddle.net/

As I said, our app is sophisticated

[ricardobeat → dustingetz]

What is the slowest part? Doesn’t look that complicated visually.

[setr → dustingetz]

Why in the world would you take over scrolling like that

Is this how you get your kicks?

[dfee → setr]

I thought, “can’t be that bad”. The clicked and it was unusable on my phone. That is bad.

[dustingetz → dfee]

What is the scroll bug exactly, or are you referring to the perf problems?

[setr → dustingetz]

On iphone sc chrome browser, what they've apparently done is completely reimplemented scrolling;

the website has its own scrollbar, on top of which chrome renders its own, and the site seems to be scrolling in place of the browser, as the "smooth-scrolling" behavior is entirely gone, as well as other little things like scrolling past the end of the page and being bumped back up

[dustingetz → setr]

ah its just a flexbox css bug, thanks for the report

[dfee → dustingetz]

No, I opened it on my iPhone X, and regular scrolling (moving my finger up / down the screen) doesn't move the webpage. Instead, I have to try and click the scrollbar on the right hand side (on my iPhone!) and then move the scroller in the opposite direction as I'd swipe.

[dustingetz → dfee]

wow, thanks