Something I support completely - previously https://news.ycombinator.com/item?id=35418933#35438029 https://news.ycombinator.com/item?id=35418933#35438029 If CS

Something I support completely - previously https://news.ycombinator.com/item?id=35418933#35438029 https://news.ycombinator.com/item?id=35418933#35438029 If CSV is indeed so horrible - and I do not deny that there can be an improvement - how about the clever data people spec out a format that Does not require a bizarre C++ RPC struct definition library _both_ to write and to read Does not invent a clever number encoding scheme that requires native code to decode at any normal speed Does not use a fancy compression algorithm (or several!) that you need - again - native libraries to decompress Does not, basically, require you be using C++, Java or Python to be able to do any meaningful work with it It is not that hard, really - but CSV is better (even though it's terrible) exactly because it does not have all of these clever dependency requirements for clever features piled onto it. I do understand the utility of RLE, number encoding etc. I do not, and will not, understand the utility of Thrift/Avro, zstandard and brotli and whatnot over standard deflate, and custom integer encoding which requires you download half of Apache Commons and libboost to decode. Yes, those help the 5% to 10% of the use cases where massive savings can be realised. It absolutely ruins the experience for the other 90 to 95. But they also give Parquet and its ilk a very high barrier of entry.