Hacker News Reader

Comment by sbov | Hacker News Reader

Depends. There's been lots of studies linking page speed to revenue. I would imagine it doesn't manifest much in lower traffic sites where there's too much noise for it to play out, but as you grow in your userbase, working fast starts to become necessary for it to work well.

View on HN

The tone of your comment sounds like you think I said one should never look at performance. I do this professionally, I should hope folks out there need performance. Let me be clear: A developer should place performance priority in the Right Place, and a good dev will know where that is.

Would you mind linking a few of these studies? I'm curious as to what the point of diminishing returns is.

nngroup [0] says that 100ms feels instantaneous. A good digest cycle run (the basic unit of Angular performance) is 16ms, a mediocre one is 20ms. So a mediocre application has 5x space to grow before the app stops feeling instantaneous.

[0] https://www.nngroup.com/articles/website-response-times/

>So a mediocre application has 5x space to grow before the app stops feeling instantaneous.

Not really. Those 100ms are from click to render done, so you also need to account for the physical transmission latency, the transmission of the data and finally the rendering (which is where your 16-20ms are).

And you upgrade your machine not when the response time goes up, but when the response time goes up too much.

And what makes it OK to burn X% additional battery life across all your users devices?

I take your general point but battery life is also a problem I have with React Native. Sure, you can drive animations from the JS thread and on modern devices in some cases you can't even tell the difference. But your battery can.

do you have any articles discussing react natives increased battery usage? why would it be any more than a native app?

Reply on news.ycombinator.com