docs(blog): blog on why DuckDB is the default backend #8378
Conversation
cpcloud
added
docs
cpcloud
force-pushed
the
why-duckdb
branch
2 times, most recently
from
81978da
to
94e59b7
Compare
ibis-docs-bot
bot
removed
the
docs-preview
cpcloud
force-pushed
the
why-duckdb
branch
3 times, most recently
from
50d2984
to
5c011eb
Compare
|
This is great, thanks @cpcloud! per https://pandas.pydata.org/about/citing.html:
could you change it to lowercase everywhere? thanks! |
There was a problem hiding this comment.
Looking good!
Some small nits.
One larger point that we can raise (but we don't have to since it's increasing the scope of the post a bit) is that, in re: memory concerns with pandas and our considerations when choosing a default backend, that general feature parity between local and remote backends was (and is) desirable.
Develop locally then go brrrr on the production system is less tractable if you have to be very careful around memory usage fo rthe local development part.
cpcloud
force-pushed
the
why-duckdb
branch
2 times, most recently
from
fd84893
to
096c122
Compare
Done!
I will add a short bit about this. |
There was a problem hiding this comment.
lgtm. I would kinda like to see something on how we think about DataFusion/Polars today -- i.e. are they great local options? would we consider switching the default?
perhaps worth pointing out if you do prefer one of them, it's easy to change the backend. but feel free to ignore
|
also timing-wise, I think we should wait to post this Monday or next Wednesday/Thursday depending on #8293 |
ibis-docs-bot
bot
removed
the
docs-preview
) Closes ibis-project#8230. --------- Co-authored-by: Cody <cody@dkdc.dev>
Closes #8230.