[halfcat]

I really like the dataframe approach. I think it’s because I like REPL-driven-development where I can drop into the REPL and work through how to transform the data interactively.

To be fair, it can nearly always be done in SQL also (unless it’s ML or some Python-specific thing like that), but the SQL with nested queries and numerous CTEs is harder for me to wrap my brain around.

If I were betting, I’d pick DuckDB, because DuckDB seems more able to implement something Polars-like, than Polars is to implement something DuckDB-like.

[bbkane]

I'm with you. I also like the IDE niceties like autocomplete and docs on hover that don't really work on SQL

[wenc]

I'm hoping someone writes a Python LSP that understands DuckDB SQL.

I use DuckDB and I typically write correct SQL, but having LSP assistance would greatly enhance my quality of life.