Hacker News Reader

Comment by lumost | Hacker News Reader

I think it's telling on the state of rust in 2021 that this project can't compile fully for the latest rust versions. Maintaining these types of frameworks in the early days is an intensive and often thankless job, having your language leave you behind is a near guaranteed way to kill off your project, not too mention introduce the obvious "I tried using library X and hit compilation issue Y type issues".

I'm curious to see how this evolves as there are a number of motivated folks working on similar efforts such as Vega. I for one would welcome a mature rust based distributed compute platform.

View on HN

> With the release of Apache Arrow 3.0.0 there are many breaking changes in the Rust implementation and as a result it has been necessary to comment out much of the code in this repository and gradually get each Rust module working again with the 3.0.0 release.

This appears to be an issue with Arrows implementation hitting a new major version and the Rust libraries not yet being compatible with the newest versions of Arrow. That's not something specific to the Rust ecosystem. It's not like a new version of Rust broke this project.

But even if it had, maintenance is always hard and the health of a project is better measured by how long it takes to be working with new, major, stable versions after widespread community adoption of those new, major, stable versions.

I don't know if Arrow 3.0 is the most commonly used implementation-- it may not have even reached that milestone.

Arrow 3.0 will be released likely in the next week. The Rust implementation has a lot of changes because we've had to make public-facing changes, mostly for performance benefits.

Thanks! This is helpful context, and supports my notion.

The project uses stable Rust. Which version are you trying to compile with?

I think maybe they were confused by this text (which I agree has nothing to do with Rust itself breaking):

Ah, yes, that makes sense. I can see how this could have been misread.

aye - it ultimately was my misreading of the commit history. Agree that this wasn't a rust specific change.

Reply on news.ycombinator.com