Probably just volume of traffic rather than the size of the assets. Not everyone's personal site is hosted on auto-scaling could services et al. So often you'll see stuff get "hugged to death" (as it's affectionately known) just due to the site's own popularity.
It's 5,000 words and 2,000 lines of javascript, plus a few fair-size images, which may explain the long TTFB. But most of the delay is not bandwidth limits but PHP and SQL. The site runs on a creaky WordPress implementation. Someday I'll fix that, if I live so long.
> Sorry. My program and your browser are not getting along. None of the interactive elements of this page will work. Could you try a different browser? Current versions of Chrome, Firefox, and Safari seem to work.
The message is very appreciated. However, the way it blends seamlessly into the text around makes it seem like a natural part of the article. At first I thought it was intentional and that the article was going to be commentary on sites that don't work well on some or most browsers. Adding something to distinguish this text from the rest, and show that there is an actual element on the page missing, may be helpful here.
(and for clarity's sake, this was triggered because I hadn't whitelisted JS on the site. It worked fine once I allowed it)
> (and for clarity's sake, this was triggered because I hadn't whitelisted JS on the site. It worked fine once I allowed it)
Oh well... Because it didn't load for me, I though it got "hugged to death" by HN.
Smart-Me™ went over to archive.org and happily discovered that it got already indexed. I skimmed the article and was confused. Obviously, archive.org does not mirror the javascript - so it will never execute. I didn't notice the message was an actual error either.
I love this type of long, interactive deep-dive into a particular topic. The site is loading veeeery slowly but it is worth waiting a minute for it to appear. So much content to ingest.
18 comments
[ 4.2 ms ] story [ 55.4 ms ] threadEdit: it did finally load. Its an interesting article and worth the wait, I thought
However the demonstrations are great, and some of the programs are inherently computationally expensive, so its sort of expected.
It's 5,000 words and 2,000 lines of javascript, plus a few fair-size images, which may explain the long TTFB. But most of the delay is not bandwidth limits but PHP and SQL. The site runs on a creaky WordPress implementation. Someday I'll fix that, if I live so long.
> Sorry. My program and your browser are not getting along. None of the interactive elements of this page will work. Could you try a different browser? Current versions of Chrome, Firefox, and Safari seem to work.
The message is very appreciated. However, the way it blends seamlessly into the text around makes it seem like a natural part of the article. At first I thought it was intentional and that the article was going to be commentary on sites that don't work well on some or most browsers. Adding something to distinguish this text from the rest, and show that there is an actual element on the page missing, may be helpful here.
(and for clarity's sake, this was triggered because I hadn't whitelisted JS on the site. It worked fine once I allowed it)
Oh well... Because it didn't load for me, I though it got "hugged to death" by HN. Smart-Me™ went over to archive.org and happily discovered that it got already indexed. I skimmed the article and was confused. Obviously, archive.org does not mirror the javascript - so it will never execute. I didn't notice the message was an actual error either.