Hacker Newsnew | past | comments | ask | show | jobs | submit | beeandapenguin's commentslogin

Was wondering the same thing. Couldn't they just load https://web.archive.org/save/{site_url} once a month in their Github action instead of managing the storage of these images?


Newton spent the majority of his life trying to answer this question. It'd be more interesting if the question asked “Will Newton’s prediction that the Second Coming won’t happen before 2060 be correct?”, but that might be a bit too long for Polymarket.



Looks like the site's down.

https://archive.is/kGmn6


Thanks for the heads up! It should be back up now


Extremely slow times - from development to production, backend to frontend. Depending on how bad things are, you might catch the microservice guys complaining over microseconds from a team downstream, in front of a FE dev who’s spent his week optimizing the monotonically-increasing JS bundles with code splitting heuristics.

Of course, it was because the client app recently went over the 100MB JS budget. Which they decided to make because the last time that happened, customers abroad reported seeing “white screens”. International conversion dropped sharply not long after that.

It’s pretty silly. So ya, good times indeed. Time to learn k8s.


Seems like a precedent for the Conch Republic https://en.m.wikipedia.org/wiki/Conch_Republic


A related article from NASA Earth Observatory has a slider to compare satellite images of the glacier.

https://earthobservatory.nasa.gov/images/152893/humboldt-gla...


This is why we need more incremental rendering[1] (or "streaming"). This pattern become somewhat of a lost art in the era of SPAs — it's been possible since HTTP/1.1 via chunked transfer encoding, allowing servers to start sending a response without knowing the total length.

With this technique, the server can break down a page load into smaller chunks of UI, and progressively stream smaller parts of the UI to the client as they become available. No more waiting for the entire page to load in, especially in poor network conditions as the author experienced from Anartica.

[1]: https://www.patterns.dev/react/streaming-ssr


I remember doing this with ASPv3 pages back in the day on a content site. It made it easy to dump what HTML has already been completed out before continuing to generate the heavier, but much less important, comments section below.


The Sphinx wasn't built with stone from a quarry, it was carved from the bedrock. It has since been restored a number of times, one of which added layers of limestone block which is easily distinguishable from the original shape.


Flint Dibble explains it a lot better than I can, around 11:00 in the video: https://www.youtube.com/watch?v=oITaI2kDIFI


At Wadi al-Jarf[1], one of the oldest harbors in the world (~2600 BCE), they discovered numerous stone anchors, a stone jetty, and storage galleries carved into limestone that contained several boats, sail fragments, oars, and rope. They also found jars that have been discovered at another site across the Red Sea, indicating they may have been used for trade.

[1]: https://en.wikipedia.org/wiki/Wadi_al-Jarf


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: