"things i learned" https://hn.algolia.com/?query=things%20i%20learned&sort=byPo...
"wish someone told" https://hn.algolia.com/?query=wish%20someone%20told&sort=byP...
"how did you" https://hn.algolia.com/?query=how%20did%20you&sort=byPopular...
I'm sure there are many others like this too!
“pm me”
“opportunity”
“pent up demand”
“I’d pay”
“I miss”
etc
The "Web Developer Checklist" was 5 years ago.
And the "quick website launch checklist" was 7 years.
Especially in places of higher latency (e.g. Australia), using JavaScript for things like this does not enhance the user experience, but rather increases the delay, because additional round trips are required, especially when it’s over TLS on a different host as in this case.
On a good connection at these latencies (~300ms), these near instant search results you describe take around four seconds to load, rather than under a second and a half as it would be if it just served the final DOM directly—or 100ms if it could serve the whole thing from an edge location. (Having to execute half a megabyte of JavaScript for a search page before it will actually do the search seems fairly absurd too.)
Subsequent searches without a page reload will also often take 2–3 seconds due to the connection having been closed and the DNS TTL being only one minute, so it’s got to resolve that again, open a new TLS connection, et cetera.
I really wish people would actively avoid the fancy JavaScript SPA approach. (And I work on such an SPA.) There’s a place for them, but this is not a good demo of that place.
