Chris

@chris.blue

37% context left

In-kernel filesystem are going to destroy the FUSE ecosystem. Bringing your custom logic into the VFS directly is absolutely incredible for performance and latency.

If you formed your opinion of agentic coding more than four months ago, I strongly encourage you to reevaluate.

Stu's talk is now available for anyone who couldn't attend South Bay Systems to watch: youtu.be/TeFsBVIYBis?... I highly recommend watching it. It's ~30 minutes and goes into details on how ParadeDB achieves faster-than-Postgres JOINs.

Generalized Consensus & ​Native Top-K Joins in ParadeDB

YouTube video by South Bay Systems

youtu.be

ParadeDB@paradedb.com · 5mo ago

On March 31st, @stuhood.sh will be speaking about how ParadeDB performs native Top K JOINs at South Bay Systems. We look forward to seeing you there: luma.com/2g3exvjw?tk=...

Feedback need: SlateDB's Python API uses pyo3, which supports Python/Rust async integration. The other bindings use slatedb-c (C FFI ABI), which is sync. Ideally, I want all bindings use one layer (FFI) to simplify maintenance. Should I ditch pyo3 and async Python support, tho?

SlateDB 0.11.0 is out! We had 5 new RFCs, 10 new contributors, and 3 new language bindings. This is a big release with a bunch of improvements and new features. 🧵

Bild

“Gradually, then suddenly.” That’s how adoption works when you’re building something new. Opendata is still "gradually" but 100 stars with $0 spent on marketing is a good start. Back to building! github.com/opendata-oss...

Bild