neat. i'm pretty novice in the guts of this kind of stuff, but how does this work under the hood for blocking operators where they "cannot output a single row until the last row of their input has been seen"?
i think this is where spark shuffling comes in? but how does it work here.
Is there a way to have the model inside of codex to make use of chunkhound instead of its “built in” search/explore functionality with rg? Whenever I spin up a new agent using xhigh thinking it spins its wheels for a while to get up to speed — wondering if chunkhound can make this process faster.
The ChunkHound docs are a bit confusing for making it available as an MCP server for Codex. How exactly do you do it? I got up to the indexing step and now need to let Codex be able to use it.
One thing that I never really see mentioned in these types of articles is that a lot of DuckDB’s functionality does not work if you need to spill to disk. iirc, percentiles/quartiles (among other aggregate functions) caused DuckDB to crash out when it spilled to disk.
I’m often surprised how little people talk about the iOS Orion browser on here and it’s ability to let you use both Firefox and chrome extensions. I’ve been using it for a while now and it’s been great. It’s a little bit buggy sometimes, but nothing that would make me switch.
My dad was diagnosed with multiple myeloma 2 years ago. His bone marrow transplant failed (frequent first line of defense) and he just finished CAR-T therapy a couple months ago. The initial side effects from the treatment were _bad_, but everything is looking good right now. CAR-T is really mindbogglingly insane cyberpunk stuff.
I had a close relative diagnosed with multiple myeloma 25+ years ago (I don't remember the exact year) who only lived for a couple more years. It was rough back then. I'm really glad to hear that there is much better treatment these days.
