Update provided<p>> Welp, figured out why - because I am idiot. Routine code change exploded performance. Only took me 2 hours to think of reverting it. Sorry!<p><a href="https://mobile.twitter.com/HNStatus/status/1402011274104360960" rel="nofollow">https://mobile.twitter.com/HNStatus/status/14020112741043609...</a>
If it’s any consolation, I thought my wireless provider had booted me before I realized HN could be having issues. It’s generally so fast and reliable that I use it as my “is my internet broken?” sanity check page.
I interpreted this much more literally. When the updated tweet about a code revert fixing it came out, it took me a second to figure out what was meant.
I don’t mean to be rude, but is HN a refutation of the Lispy vision it was meant to demonstrate? There has been a bug where comment pages can only show a limited number of entries for years, and the wonderful mods like dang continually report it is being worked on. It’s hard for me to believe it wouldn’t be fixed much faster if it occurred in a more practical language.
BeOS came up with an function for this: <a href="https://www.haiku-os.org/legacy-docs/bebook/TheKernelKit_SystemInfo.html#is_computer_on_fire" rel="nofollow">https://www.haiku-os.org/legacy-docs/bebook/TheKernelKit_Sys...</a> but “Smoldering doesn't count.”
I had an older Dell give up the magic smoke recently and literally - <a href="https://i.imgur.com/WHYODQS.jpeg" rel="nofollow">https://i.imgur.com/WHYODQS.jpeg</a><p>Amusingly enough I smelled it weeks ago and it finally shut off a few days ago.
If you think about it, it's impressive how such a high traffic site works out using a niche language which what I assume is not such a big ecosystem.<p>(On the other hand there's moderate complexity but low page sizes and nothing like modern websites with hundreds of cookies, heavy js, etc)
I really thought it was going to be someone complaining about their restaurant server having a smoke break. Thought it must have been covid related to make the front page. But don't ask me how.
My google foo failed and I wasn't able to find the correct @hnstatus account when I was having trouble. Perhaps a ”status" link in the footer would make this easier to find?