Assumes that a project moves beyond 10s of GBs. I guess 99.9% of projects that import pandas fall well below this threshold.
If a library is performant at large datasets, it is likely performant at small ones too.
This isn't a call to arms to rewrite everything in the new shiny, just consider the new shiny for new shiny things
I'd write more tutorials about how to use data science tooling but one consequence of AI is that all the old data sources I used to analyze such as social media and Reddit are now completely locked down (I am surprised NYC Taxi is still being updated, though). Therefore in the meantime, I'm working on making better data science tooling...although unclear to what end due to the data issue above.
In many cases I’ve found directly using python primitives to be less confusing than pandas.
Similarly, in companies I’ve worked at, the datasets just aren’t that big. Especially if you’ve got access to modern hardware.
https://eddie.codes/posts/pandas-should-go-extinct/ <=> https://eddie.codes/posts/source-code-comments/
Published two posts at the same time and total PEBCAK
Something going wonky on their blog, where two posts got their links swapped.
DuckDB on the other hand is wonderful and truly doesn't use any more memory than it really needs to.
Hoping OP can fix this on their end so the url has the expected content. Whoops!
The problem is, orgs who see themselves as big data orgs want to act that way, even if they're medium data. "But we'll need it when we grow", "we need to know the state of the art tools"
If I still need to do db-like things in python I think duckdb is better.
Vaslo•35m ago