> Apart from that, we've renamed cacheTime to gcTime to better reflect what it is doing
Does it though? Maybe it's super obvious to more experienced users, but now I need to read the docs to find out what "gc" stands for. Not a big deal, just seems like an unnecessary abbreviation, so I'm curious as to what the reasoning is.
which is likely much better than making the wrong assumption because you know what "cache" means. Check the docs, cacheTime is very likely not doing what you expected.
A typical expectation would be that "cacheTime" controls how long react query uses the cached value before it tries to fetch that data again from the server. That part is actually controlled by "staleTime".
so cacheTime was really confusing because it seemed like "this is the amount time we cache data for", but that's not what it is. So a rename had to happen. We had some discussion on the public roadmap (https://github.com/TanStack/query/discussions/4252) about what it's gonna be. I'm usually against abbreviations, simply because there's always someone who doesn't understand what it means. But all other suggestions like inactiveCacheTime also had room for interpretation. gc is an abbreviation that is known well enough (think git gc), and it's also not an option that you will customize on a daily basis (usually once, globally).
In a similar vein, "Chip War" by Chris Miller is a more recent look at this. Not at all as dry as I expected it to be, surprisingly gripping for someone who didn't previously know much about this. It also provides a lot of historical context for the recent news of TSMC setting up factories in the US and Germany.
I thoroughly enjoyed "the chip war". From the history perspective, the technology perspective, the politics and even the human side of it. How people growing up in the misery of ww2 went on build something that ended up shaping the world we live in.
Ooh! Subscribed, and just finished the Montaigne segment a few seconds ago.
Runciman's "History of Ideas" series on political thought was excellent, and pairs well with a number of other philosophy podcasts I follow (Peter Adamson, Stephen West, Cecil Adams, Nigel Warburton, amongst others).
Absolutely. Like so many things, Private Eye is ahead of the curve in its reporting. Another podcast worth a mention is James O'Brien's recent Full Disclosure interview with Grenfell survivor Edward Daffern. Horrifying to hear how the residents were treated before, during and after the tragedy, and how predictable the whole thing was.
Worth remembering Private Eye are biased towards insinuating institutional corruption, leading to their support of Wakefield against the pharmas in the MMR scandal.
They are generally good, but they aren't immune from bias and it still pays to be critical.
Yeah this piece was a huge piece of inspiration for me when I was learning Csound. I actually had a chance to ask BT about this particular piece once and if the rumors were true about it being all done in Csound. The guitar riff you hear halfway through the piece is actually sampled and played via the diskin opcode. Other than that, all Csound. Still a very impressive feat, especially considering the fact that the piece itself was originally mixed in 5.1.
Nice! I'd wondered about that guitar, it sounds impossibly real to be pure Csound. Thanks for the insight. And yes, I had the opportunity to listen to the whole album on a decent 5.1 system at uni a while back and it's pretty spectacular.
Does it though? Maybe it's super obvious to more experienced users, but now I need to read the docs to find out what "gc" stands for. Not a big deal, just seems like an unnecessary abbreviation, so I'm curious as to what the reasoning is.