I don't think I would ever consider RSV and Parquet alongside each other. I also don't think I've ever personally had a use case where the proposed RSV format w

I don't think I would ever consider RSV and Parquet alongside each other. I also don't think I've ever personally had a use case where the proposed RSV format would have been a good fit. Nevertheless I found it interesting. Even if you were to use FS, GS, RS, US, they are all parts of valid UTF-8 strings. I agree that they would be vanishingly rare in most corpi of "ordinary text". The author here is also aware of them.[0] I found it quite an interesting idea to use bytes that are invalid in UTF-8 strings as delimiters for data that is guaranteed to be encoded as UTF-8 strings. This moves those control characters properly out of band. Out of band is a much stronger guarantee than vanishingly rare. I don't think I'll use RSV anytime soon, but I appreciate the creativity that went into it, as well as the many implementations the author has already collected[1]. There are 31, by my count, including several that support larger ecosystems: C (everything can call into C), C# (dotnet runtime and other languages, such as F#), Java (JVM languages, such as Clojure), JavaScript (any of the many compile-to-JavaScript langs, such as TypeScript). [0]: https://github.com/Stenway/RSV-Specification#why-dont-you-use-ascii-control-characters-like-the-record-separator-0x1e https://github.com/Stenway/RSV-Specification#why-dont-you-us... [1]: https://github.com/Stenway/RSV-Specification#how-will-rsv-gain-adoption https://github.com/Stenway/RSV-Specification#how-will-rsv-ga...