If you store the latest state on your server it would load instantly, and you would not be wasting electricity by repeating the work on all your users’ devices. Using artistic flourishes to cover up bad engineering is decidedly not brutal: brutalism is all about the engineering itself being the artistic flourish.
I mean doing it on a different server would just be useless, that’s what the original site already does. I’m also not really sure how this would work do to all of the cache invalidation issues that would occur as comments are added.I don’t really have the financial backing to run a real time in memory cache of all HN for free, which in effect is what HNs API already does. I recommend actually reading the docs on how their API works and it’s quirks. Besides the point, this wouldn’t be able to be hacked into 1 HTML file which I wanted to do for the challenge
Also, if my site is “wasting electricity” that means every other HN reader is too because that’s how their API works! This is by far the silliest comment I have received!
The whole point of this project is also that there is NOT a server, and the site I created functions as a mobile/tablet/desktop app too
