duckdb-rs 1.3.1 is the first release I was involved in. Expect many more to come! 🤘
We also plan to implement changes that will allow us to publish new crate versions without waiting for the next DuckDB release.
github.com/duckdb/duckd...
Ive touched on this a couple times, but in short I think it would be very hard to put raster processing into duckdb and maintain acceptable performance/memory usage. Huge blobs (rasters) and vectorized execution does not go well together. E.g. a single duckdb vector with 512x512x4 tiles is 2GB RAM.
As for the linux issues, thats a more general problem with all sorts of binary distributions on linux, which is why we're following pythons footsteps and using the many-linux system images when compiling. There's more details e.g. here peps.python.org/pep-0513/
AFAIK the extension side of the C-API doesn't require any c++ code to function, you could theoretically just program against the header without any linking with all the api callbacks passed as function pointers at runtime. That's why we're generally trying to (slowly) invest more in the C-API.
