11–20 of 35 posts
why would you use this over duckdb?
Disclaimer: I work at ClickHouse
I absolutely love this trend of "pip install x" as a distribution mechanism for this kind of thing. People badmouth Python packaging a lot, but once you've learned how to use a virtual environment (admittedly a steeper learning curve than I'd like it to be) having binary wheels for so much of this kind of stuff is a huge win. See also Playwright, DuckDB, ziglang... I wrote a bit about those here https://simonwillison…
And the fact that it's not easy to use doesn't really make things better.
why would you use this over duckdb?
why would you use this over duckdb?
Note chdb is based on ClickHouse codebase but completely community powered so there's no feud with DuckDB (I'm a quackhead, too!) which actually offers lots of great inspiration and many integration opportunities with ClickHouse/chdb for combined compute and processing of datasets. I personally love both and use them together all the time in my colab "OLAPps"
I absolutely love this trend of "pip install x" as a distribution mechanism for this kind of thing. People badmouth Python packaging a lot, but once you've learned how to use a virtual environment (admittedly a steeper learning curve than I'd like it to be) having binary wheels for so much of this kind of stuff is a huge win. See also Playwright, DuckDB, ziglang... I wrote a bit about those here https://simonwillison…
Do they provide wasm version to use in browser? (like duckdb-wasm)
I absolutely love this trend of "pip install x" as a distribution mechanism for this kind of thing. People badmouth Python packaging a lot, but once you've learned how to use a virtual environment (admittedly a steeper learning curve than I'd like it to be) having binary wheels for so much of this kind of stuff is a huge win. See also Playwright, DuckDB, ziglang... I wrote a bit about those here https://simonwillison…
I absolutely love this trend of "pip install x" as a distribution mechanism for this kind of thing. People badmouth Python packaging a lot, but once you've learned how to use a virtual environment (admittedly a steeper learning curve than I'd like it to be) having binary wheels for so much of this kind of stuff is a huge win. See also Playwright, DuckDB, ziglang... I wrote a bit about those here https://simonwillison…
I'm tempted to say that the very same reason why you need different environments is precisely because the package system is not healthy. And the fact that it's not easy to use doesn't really make things better.
I think Python's biggest weakness on this front is mainly that virtual environments came along too late - if they'd been designed into how pip etc worked from the beginning we would be in much better shape.
Do they provide wasm version to use in browser? (like duckdb-wasm)