11–20 of 87 posts
I mean... is it? It feels a _lot_ slower than it used to, especially on slower devices. Possibly that 700kB of random crap is implicated :)
Classic HN. Snarky, condescending and nothing of substance. Reminds me why I visit HN less and less lately.
In my testing, I'd set a breakpoint on my server code to see when I'd get the "push" from Twitter's API and would use the Twitter App on my phone to create test tweets. Every single time, I'd create a tweet and my server breakpoint would be hit immediately. Not soon, but immediately. I'd see my breakpoint triggered well before the UI in the app even refreshed after submitting the tweet.
It feels fast because most other sites are insanely slow. Just build a normal HTML+CSS+JS site with serverside rendering, route the assets through a CDN and voila! your site will be just as "fast" as Google.
Then try to load https://cr.yp.to
Ok now try to do a google search for dog food.
Tell me which one executes in less than a second, and which one hangs forever
Earlier quoted context omitted.
I don't think you read the article. Devtools shows 130 requests because it considers inline data URIs to be a request--instead, there are lots of inlined images. so the page looks mostly complete with only the original document request.
I did read the article that's I picked to sentences from there. I did not pick up from the article that chrome counts inline data as requests and I did not know that earlier. I find that even more odd that inline data is counted as requests. edit: stand corrected, thanks for pointing out
It feels fast because most other sites are insanely slow. Just build a normal HTML+CSS+JS site with serverside rendering, route the assets through a CDN and voila! your site will be just as "fast" as Google.
Edit: I was too quick to judge your post. The article is indeed just about serving content, not about why their results are fast.
Climb to the top of a mountain in the USA (or live in the countryside of a developing country), where you can only get 1 bar of 3g service. Then try to load https://cr.yp.to Ok now try to do a google search for dog food. Tell me which one executes in less than a second, and which one hangs forever
Just compare the google page load if you want to compare with that ?
To me it feels like an oversight when answering the question “how the hell is Google so fast?” and not digging into how Google is able to return the results to your actual search query in a matter of milliseconds. That, to me, is the real miracle.