Ballista: Distributed Compute with Rust, Apache Arrow, and Kubernetes

Re:Ballista: Distributed Compute with Rust, Apache Arrow, an... by pjmlp on Wednesday July 17, 2019 @06:14AM (#20457965)

Rust still has to do some work regarding language ergonomics.

Currently I rather wait for Java to get its value types story properly done.

For me an ergonomic future is a tracing GC, value types and manual memory management in hot code paths, like D, Eiffel and Modula-3 are capable of, improved with ownership rules.

[ Parent | on HN ]

Re:Ballista: Distributed Compute with Rust, Apache Arrow, an... by 0815test on Wednesday July 17, 2019 @06:35AM (#20458048)

Conventional tracing GC is antithetical to Rust's zero-cost goals. The community is currently working on things like deterministic collection of reference cycles, e.g. https://github.com/lopopolo/ferrocarril/blob/master/cactusre... which should address the same use cases perhaps even more effectively.

[ Parent | on HN ]

Re:Ballista: Distributed Compute with Rust, Apache Arrow, an... by pjmlp on Wednesday July 17, 2019 @06:52AM (#20458128)

Right, but if productivity suffers, vs what tracing GC + value types + manual memory in unsafe code, are capable of, then Rust will mostly take over device drivers and kernel code, not userspace apps.

Which is what is currently happening to C++ across all major OS SDKs, being driven down the OS stack.

[ Parent | on HN ]

Re:Ballista: Distributed Compute with Rust, Apache Arrow, an... by twic on Wednesday July 17, 2019 @07:59AM (#20458464)

I hope so! The Rust leadership's quixotic quest to turn it into a language for the server-side may delay this, though.

[ Parent | on HN ]