<- Back
Comments (36)
- benrutter> We don’t aim to make a big feature release of Polars 2.0. In fact we hope it to be a boring experience for you. The reason we bump this major version is that we can get rid of design decisions made in the past that currently block us and then we want to change defaults to more sensible settings that will benefit a greater audienceI know this take reveals me as a very dull person, but I love seeing projects take semver seriously like this! Version bumps should really be about removing deprecated cruft rather than shiny new features.I've used polars for a while now, and their focus on stability was a big part if convincing me to make the jump initially!
- KydlawHappy to see activity around Polars. This has been my go-to library for data processing due to the enhanced ergonomics compared to Pandas and SQL.But they were a bit quiet lately, and I started looking more and more into DuckDB recently… until the recent acquisition of DuckLab by AWS
- bobson_dugnutt5I love polars. Did a lot of evangelizing in work to get people to give up pandas in favor of it.
- bluebarbetWhat does this project have to do with Serbia? Are the developers in Belgrade?
- arn3nThe decision to default to the streaming engine is really interesting. My intuition is that this would be slower than other data frame operations that are more parallelizable with batch processing, because streaming engines necessarily process rows sequentially. Is my intuition off/am I overestimating how much auto-parallelization polars does?
- rfgplkSeeing "release will land in the following weeks" kind of immediately turns me off.