blindmute
Joined 5 years ago
Joined 5 years ago
If calendars really did advance 300 years, we are living past the advance. That means that when we see a writing reference an eclipse that we know happened in what we call 900, it doesn't actually tell us anything about the calendar having moved or not. It only tells us that something was observed 1122 years ago. That could be 900 years after 0AD, or it could be 600.
Actually, almost every instance of dating anything back then depends upon few relative date calculations which are "known". The eclipse happened 1000 years ago, so that is year 1022, and this writing referencing it is from 1022, and so this scholar writing a generation later is from 1082. This inscribed rock was found under 1100 years of dust, so the people living here were from 922, and their language existed at that time, and all records we find from this civilization are now known to be from the early 900s. Now we can claim to have evidence that there was thriving commerce in the 900s with hundreds of written records about it, so of course the dates weren't changed.
If you dig into the records people cite as evidence against the phantom time hypothesis, the vast majority of them (literally every one that I've seen) is using indirect dating in this way, which doesn't mean anything.
Its role is to do everything you just said in one package, plus other networking features. It fetches, updates the store, subscribes the components, caches the responses, performantly rerenders. It allows configuration of when to refetch, how to cache, polling, pagination, infinite scroll, etc etc via a simple API.
Nothing is stopping you from writing all this yourself, but libs exist for a reason. It's a terribly useful networking package. If you just use a generic store and write a fetcher yourself, you have to at the very least write logic for when to (re)fetch and for persisting the responses to the store.
Without this feature, every component needing remote data D must share a parent ancestor fetching D for all of them, even when the children are not conceptually related. Adding another component higher in the tree means you have to hoist the fetcher up to that level, etc. React query is an incredible upgrade to anything else I've used over the years.
If you remove those units at the start, you've reduced the starting temp a bit, but you haven't much changed the long tail of the cooling. You essentially just started the coffee at a slightly cooler temperature, but this doesn't affect the curve much. Or to think of it another way, the change in temperature at the start corresponds to a small amount of X axis (time) on the curve.
If you add the cream later, the temperature reduction corresponds to a larger amount of time on the curve. This means the temperature will be lower than the above.
So to my intuition, cream first should yield hotter coffee
1. We already produce way more food than the entire world can eat, even if it were distributed equally
2. When population begins butting up against the limits of food production, demand for cheaper plant based food will rise. Most will be unable to afford meat, making the meat market naturally shrink itself for economic reasons. Likewise if meat becomes too expensive due to resource constraints.
3. At the point where population exceeds food supply, there will be at worst 1 generation of starvation, and then population will stabilize to have enough food
3a. Infinite growth of the population is not sustainable or desirable. Even if meat were banned, this same story will eventually happen again with any vegetable that is less calorie efficient to grow. Do we want 30 billion people eating literally one food, or 25 billion eating a varied, though less land efficient diet? At some point, the world will have to accept that there isn't enough food to have 3 children. At that point, when the 2 child policy is global, what kind of diet should be possible? We can stretch it so that we're all eating literally one crop and there's absolutely nothing more we can do to feed the world, but hopefully we stop breeding a bit earlier than that, to end with one where people can still enjoy meat.