<story><title>Conservative web development</title><url>https://drewdevault.com/2018/09/04/Conservative-web-development.html</url></story><parent_chain><item><author>coding123</author><text>There are two different kinds of web development:&lt;p&gt;a) Apps where the user is expected to stay a while&lt;p&gt;b) Sites where the user is there, maybe once ever (most likely also scared off by the ads)&lt;p&gt;For Apps, I would always prefer a pre-load of JS that was built with React and downloads about 2-4 MB. If there is an update I will be forced to download it again.&lt;p&gt;On the UPSHOT, almost everything I do in that app is now a 3-8KB request. This means transitioning pages, changing states of things, all happen in about 50ms including whatever visual changes are required on the screen.&lt;p&gt;Compare that to full-screen refresh apps and I am usually waiting 200-400ms. It just feels too damn slow.&lt;p&gt;Why am I even typing this? This is the freaking whole point of an SPA. Are we not all caught up on this yet?</text></item></parent_chain><comment><author>trolleyhacker</author><text>As long as web designers and developers continue to target imaginary users or themselves, they&amp;#x27;ll also leave real users wanting more.&lt;p&gt;Great, you&amp;#x27;ve shaved off 150-350ms of refresh load time. So why does your website take 10-15 seconds to load on my phone when I&amp;#x27;m walking about the supermarket?&lt;p&gt;Get out of the lab. Start testing with real users in real contexts. You&amp;#x27;ll quickly learn that many of your assumptions about what users want disappear.</text></comment>
<story><title>Conservative web development</title><url>https://drewdevault.com/2018/09/04/Conservative-web-development.html</url></story><parent_chain><item><author>coding123</author><text>There are two different kinds of web development:&lt;p&gt;a) Apps where the user is expected to stay a while&lt;p&gt;b) Sites where the user is there, maybe once ever (most likely also scared off by the ads)&lt;p&gt;For Apps, I would always prefer a pre-load of JS that was built with React and downloads about 2-4 MB. If there is an update I will be forced to download it again.&lt;p&gt;On the UPSHOT, almost everything I do in that app is now a 3-8KB request. This means transitioning pages, changing states of things, all happen in about 50ms including whatever visual changes are required on the screen.&lt;p&gt;Compare that to full-screen refresh apps and I am usually waiting 200-400ms. It just feels too damn slow.&lt;p&gt;Why am I even typing this? This is the freaking whole point of an SPA. Are we not all caught up on this yet?</text></item></parent_chain><comment><author>zelon88</author><text>Your math sounds wrong, so I did it on paper and proved that it&amp;#x27;s wrong.&lt;p&gt;The average bandwidth for a mobile device in the USA is about 3.25 mb&amp;#x2F;s (26mbps). So to load your &amp;quot;2-4mb&amp;quot; Javascript library you&amp;#x27;re looking at 400ms to connect + 1000ms to download resources. That&amp;#x27;s 1400ms.&lt;p&gt;Now for the rest of the math I benchmarked my own website. My homepage is ~300kb and loaded in 461ms. The fastest you&amp;#x27;re going to get ANYTHING back from my server is about ~170ms.&lt;p&gt;Lets start with your App. 1,400ms and the app is loaded. Load another page and it takes 200ms to load another 5kb of content. Load one more page and it&amp;#x27;s another 200ms for 5kb of content. I&amp;#x27;ve been waiting on your website for a total 1,800ms and viewed three &amp;quot;pages&amp;quot; of content.&lt;p&gt;Lets move on to my website. ~450ms and the site is loaded. Load another page and it takes another ~450ms to load another 300kb. Load another page and that&amp;#x27;s another ~450ms to load another 300kb. I&amp;#x27;ve been waiting on my website for a total of 1,350ms and viewed three actual pages of content, but the user only had to download 900kb instead of 4mb.&lt;p&gt;So I think you proved the OP&amp;#x27;s point.</text></comment>