Recent and related:<p><i>Modern Polars: A comparison of the Polars and Pandas dataframe libraries</i> - <a href="https://news.ycombinator.com/item?id=34275818" rel="nofollow">https://news.ycombinator.com/item?id=34275818</a> - Jan 2023 (62 comments)<p>Also:<p><i>Polars: Fast DataFrame library for Rust and Python</i> - <a href="https://news.ycombinator.com/item?id=29584698" rel="nofollow">https://news.ycombinator.com/item?id=29584698</a> - Dec 2021 (124 comments)<p><i>Polars: Rust DataFrames Based on Apache Arrow</i> - <a href="https://news.ycombinator.com/item?id=23768227" rel="nofollow">https://news.ycombinator.com/item?id=23768227</a> - July 2020 (1 comment)
I think its really interesting such gems offering a ruby layer on top of rust libs. One issue that I have with that is - and maybe it's my ignorance - but is that necessary to bundle the original lib as <a href="https://github.com/ankane/polars-ruby/tree/master/ext/polars">https://github.com/ankane/polars-ruby/tree/master/ext/polars</a> ? I can imagine that makes easier to avoid breakage, or with C extensions, because you dont have some dependency manager around, but couldn't we sort it with Cargo? For instance, having the version locked and it could download (and cache) the dependency when necessary?