3 ms·
Announcing Polars 1.0 (Blog Post)
- deleted 2y ago[deleted]
- jeffbarg 2y agoIt's interesting that they are explicitly not committing to holding the API constant (which seems quite common & expect for a "1.0"). I generally like that philosophy, but I wonder if it will lead to some unexpected whiplash in the future for people now expecting the core to be stable.
- milliams 2y agoIt's a bit unclear in the docs, but I think what they're saying is that if there's a need for a breaking change, they're "not afraid to release version 2.0", rather than saying they're "not afraid to make a breaking 1.x release".
- fbdab103 2y agoPolars is already effectively Pandas 2.0 with a lot of lessons learned. Hopefully, there is not too much additional churn.
- jmakov 2y agoAny examples od how to run it on a GPU?
- reaus 2y agoIt is still in development AFAIK. They did an announcement, but no news on the actual release yet
- simicd 2y agoYes only found the announcement [1] that the Polars team and NVIDIA engineers are working on a GPU engine, but other than that no concrete examples. Github issues also don't provide any hints on the status, only one open item [2] where most comments are prior to the announcement. [1] https://pola.rs/posts/polars-on-gpu/ https://pola.rs/posts/polars-on-gpu/ [2] https://github.com/pola-rs/polars/issues/13111 https://github.com/pola-rs/polars/issues/13111
- rcarmo 2y agoPolars has been my go-to for six months now. The performance gains for what I do are pretty great, and the ability to write out Parquet with minimal hassle is just dandy. If it weren’t for resume-driven architectures, it would make a great alternative to Spark for high volume bronze-to-silver cleanup and normalization steps.