Writing a small ray tracer in Rust and Zig

Re:Writing a small ray tracer in Rust and Zig by the_duke on Tuesday July 02, 2019 @08:40AM (#20334421)

I agree and I'm not advocating for Rust's std to gain things like http clients or template engines.

But some parts of the ecosystem end up in a lot of projects. Conservatively extending std would be good for the language, IMO. To set a standard, reduce compile times, and ease the burden for companies that have hard review requirements for each dependency.

Some things I'd like to see in std in a few years:

* `serde`

* `rand`

* `log`, but probably without a backend, or a simple default

* a subset of `chrono`

* some parts of `rayon`

[ Parent | on HN ]

Re:Writing a small ray tracer in Rust and Zig by eridius on Tuesday July 02, 2019 @02:16PM (#20337843)

I think we could strike a balance. Don't put this stuff in the standard library, but have a category for crates that are officially blessed (or even maintained by) the core team, such that if you trust the Rust stdlib then you should be comfortable trusting these crates. Then provide binary distributions for the built crates for all tier 1 platforms at least (ideally for any platform where a binary distribution of the stdlib is available) and teach cargo how to download those. This way we maintain the ability to version these crates and have breaking changes, but without the overhead of having to recompile these crates.

[ Parent | on HN ]

Re:Writing a small ray tracer in Rust and Zig by Sean1708 on Tuesday July 02, 2019 @09:22AM (#20334688)

What about a set of "blessed" crates (that can only depend on other "blessed" crates) that are maintained by the language developers? Seems like the best of both worlds to me.

[ Parent | on HN ]