14 comments

[ 2.5 ms ] story [ 31.2 ms ] thread
(comment deleted)
How does this compare with delta lake and iceberg?
how does this compare to Arrow IPC / Feather v2?
The cuDF interop in the roadmap [1] will be huge for my workloads. XGBoost has the fastest inference time on GPUs, so a fast path straight from these Vortex files to GPU memory seems promising.

[1] https://github.com/vortex-data/vortex/issues/2116

Can you explain how it’s faster? GPU memory is just a blob with an address. Is it because the loading algorithms for vortex align better with XGBoost or just plain uploading to the GPU?
Can we stop with the cringe emojis at the start of every heading?
I guess not surprising from a project that combines Polars & Vortex
I tend to agree, but I don't see this one as any of the worst offenders, unless I am missing something.

This readme has what, max two or three emojis? Compare that to most LLM generated readmes with a zillion of emojis for every single feature.

Can you append new columns to a file stored on disk without reading it all in mempey? Somehoe this is beyond parquet capabilities.
(comment deleted)
One thing I found interesting is the logical type system doesn't seem to include sum types or unions, unlike Arrow etc.

I'd generally encourage new type systems to include sum types as a first-class concept.