Hacker News
points by whizzter 3 days ago | 0 comments
I kind-of like it, spontaneously taking tables from CSV files doesn't seem to be there (there's a mention of parquet via dataframes so perhaps it's supported implicitly, but maybe add that documentation?).

I see that import/export pipelines are there, so transform pipelines should be simple, and I guess that's a quick-n-dirty usecase it's there for (the spreadsheet part of "taco-bell programming" ala Dziuba ?).

Personally though for me often, the spreadsheet's interactive and quick recalcs is the important part, the exploratority quick checks with numbers updating, now if it can take arbitrary sheets and get out all "unstructured" calculations so one can edit them more properly later it's a win, or am I missing other major usecases?

[–] librasteve 2 days ago
that a gap in the doc … as of today (in test) uses the Polars csv import same s parquet

still working out the use cases more thoroughly, for now i would say that they range from ad hoc calculations (like a quick thrown together Excel), though LLM workflows (markdown centric reports with numeric calculated tables) to 1GB+ dataset ingestion and interactive analysis

Hacker News