Re:Writing a small ray tracer in Rust and Zig
by xiphias2 on Tuesday July 02, 2019 @05:38AM
(#20333555)
When I search for the Python dead batteries problem, the main issue is that the Rust developers don't want to maintain a growing list of libraries forever, especially that some of them will be depreciated over time.
This is totally understandable position, but it is still important to have sensible defaults for common tasks for end users.
One example that I can point to is Haskell, which I tried to learn from Haskell books, and it took me years to realize that it's not the language that's extremely inefficient, but the default libraries that use lists instead of arrays for most of the tasks.
I'm writing about Rayon because I see it as a reoccuring discoverability problem for people who are new to Rust.
There are many possible solutions, but one would be to have a default list of dependencies created in Cargo.toml that can of course be modified by the Rust users. Also that list can of course be changed over time by Rust developers.
This is totally understandable position, but it is still important to have sensible defaults for common tasks for end users.
One example that I can point to is Haskell, which I tried to learn from Haskell books, and it took me years to realize that it's not the language that's extremely inefficient, but the default libraries that use lists instead of arrays for most of the tasks.
I'm writing about Rayon because I see it as a reoccuring discoverability problem for people who are new to Rust.
There are many possible solutions, but one would be to have a default list of dependencies created in Cargo.toml that can of course be modified by the Rust users. Also that list can of course be changed over time by Rust developers.