You're ignoring the method by which these things are dated. First, if a date was written on the page (extremely rare), it may well have been after the date change happened. The vast majority of writings from the time are dated to known events, like eclipses, or by reference to other known things ("20 years ago, when Joe was born" and then finding Joe's birth records).
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.
It's a great benefit for a component to be able to specify what data it needs from remote without worrying about if an ancestor or sibling also needed it. React query will only fetch once the unique queries in the whole tree.
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.
An external service fetcher doesn't have integration with React because the entire tree potentially needs to know when the data changed. Once you write the code to subscribe to those changes where necessary, you've basically invented another state library.
* Service fetcher does fetching and updating store
* Component does subscribing
* React does updating component tree with changes.
If a component wants changes it must subscribe. If not, it doesn't.
If there is a change, subscribed components get updates. If not, they don't.
Responses are (conditionally) cached in the store by its respective service. Any component that wants data just asks the service. Service fetches from the store or remote. I can customize and unit test the the service.
I don't see the overlap in responsibility between any state lib (react or whatever in this case) and the purpose built service.
You’re hand-waving away “subscribing” as if it’s not a time bomb.
The set of possible events any given query might need to subscribe to is massive. Yes, you can build a large app with a pub/sub model but the number of subscriptions runs away from you and it gets really hard to know which of 1000 subscriptions you need to refresh when an association between two random pieces of data is created/deleted.
Associations are where you really get screwed IMO.
That said, despite exploring lots of possibilities I don’t think there’s any perfect way to do this automatically. So while I think you’re hand-waving away a hard problem, I also think your proposed solution is probably one of the better ones.
Still, I don’t think you should pooh-pooh people trying to solve the general problem. It’s a worthy one.
Being hard to define and manage subscriptions is a problem, a bigger deeper problem that react query or any other lib isn't solving.
By "set of possible events any given query might need to subscribe to is massive" i assume you meant "component" and not query, if not then i don't know what that means, if yes, that component needs refactoring.
I'm interested in libraries not because of what it can do for my code or me or my team but what problem it solved for the team that needed it in the first place, bad enough to write a lib for it. I want to avoid those problems.
I start with importing libs for quick TAT and slowly replace them with a few hundred lines of code that i can understand, modify, debug, monitor, unit and integration test. I usually end up redefining or better defining the problem and rescoping the issue to not needing to solve said problems.
Most libs do NOT provide that level of valuable solutions to worthy problems to go keep them around as deps. Deps are not free and have no liability to me or my code. React query is one more in that long list. IMHO.
I do mean “query”. I am presuming you want every query in your app to live update when the results change. The problem I’m indicate is: how do you know which queries are invalid after any given event?
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.
My reasoning is that the coffee will cool in a curve having high rate of temperature change at first, and slower later in a long tail until it reaches room temp. Adding the cream will "remove" a fixed amount of "heat units". The heat of the cup can be graphed as heat/time and it will look like exponential decay.
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
It would also help the planet greatly if we stopped sending aid to Africa and other poor nations. Without our help, their populations would decline quite a bit, reducing their meat consumption and emissions by a huge amount. I know this is an unpopular sentiment but we have to be pragmatic.
It's not about per capita, it's about total. We can not only reduce their resource usage, but also produce less food ourselves, all for free. It's win-win.
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.
There's simply no empirical evidence that you love your wife/mother, so it would be foolish to believe that you do. Until a study is funded there's just no way for you to know. Trust science
Because the country was explicitly founded in a way that local matters more. If you want abortions, go to an abortion state. Is it so intolerable that Mississippians as a whole want different things than you and your state residents do?
Then wanting to do things differently is fine of course. The problem I have is that Mississippi receives $7,000 more from the federal government than they pay per capita every year. Bringing unwanted children into the state will make that worse. Why should they get to collect my tax dollars and then make decisions that cause the rest of the country harm?
If we only want profitable people represented, we can skip the extra steps and just have a voting fee, or even just a landowning requirement! Then the poors won't be able to screw up the country at all
This is exactly how things should work. If you don't like the politics of one state, you should move to another state. States should retain authority over their laws not enumerated in the constitution. The diversity of states, some with weed, some with no income tax, some with abortion, some with an oil stipend, is a great thing. Hopefully most companies end up supporting this
Hmmm, if it wouldn't pass the Senate then I guess a lot of states' constituents don't want this. Sounds like it's better left to a state by state basis.
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.