rs_pbrt VS Iron

I just released a first version of blend_info on crates.io. At some point I was working on a similar project on codeberg and I kind of hacked that into rs-pbrt to be able to use some binary Blender .blend files directly as input for my physically based renderer. The executable for that is called parse_blend_file file and details (or a video about it) can be found here. Anyway, the new crate should help parsing any Blender file (independent of the version) and extract information you like to use, kind of cherry picking stuff. I will use the library in a future version of parse_blend_file (as a prove of concept) but want to involve other people early, because they can help me defining a re-usable library, which can be used for many things, not just my renderer. I also started to use sourcehut and investigated how to use CI (building currently for Debian) there, provide mailing lists, and use the (project based) ticket system. Both projects and activity around it can be found here. Most likely I will work on documentation and maybe a blog post about how to use blend_info next. Try to register for one of the mailing lists if you want to contribute and/or create a ticket ...

If somebody is interested in helping with this issue, there is something to learn from the artistic side (Blender users) as well as from the programming side (Rust coders).

https://www.rs-pbrt.org/ - Physically based rendering (PBR) with Rust

Big thanks to wahn/rs_pbrt: Rust crate to implement a counterpart to the PBRT book's (3rd edition) C++ code. See also https://www.rs-pbrt.org/about ... (github.com) and abusch/rustracer: A toy raytracer written in Rust based on PBRT (github.com) which where helpful as references.

I've written many things using Iron and it's been fine. It's not particularly developed any more but I am not aware of any major outstanding issues.

I don't miss the time when we basically only had Iron

iron

There're many web framework in rust, such as SergioBenitez/Rocket , actix/actix-web ,poem-web/poem , iron/iron . How do I chiose, anyone suggestion？

I'm not sure which definition of backend you are thinking of here. In case you simply mean "server side", here are a couple of libraries that might be of use: iron - been a while since I used it, used it for a couple smaller projects rocket (nightly only) - no personal experience, but a lot of people seem to like it diesel - a bit complex to wrap your head around, but once you get the idea it's really nice. Definitely check out the examples.

it's taken by a web framework https://github.com/iron/iron

Your comment touches on a few misconceptions I see a lot.

Firstly, `reqwest` exposes both an async and a synchronous API, allowing the developer to choose which one to use. They are largely interchangeable code-wise. [1]

Secondarily, and more broadly, async is possible to opt out of. You must understand that most web and network related libraries will be async by default for performance, because people who write in Rust and people who write web servers typically care greatly about performance. This is the intersection of those two groups. That being said, there are options outside of that ecosystem. [2]

If you truly want to use an asynchronous library without migrating your application to run entirely on an async runtime like tokio, you can run it inside of a synchronous function without much trouble. I've put together a playground link for you. [3]

1. https://docs.rs/reqwest/0.11.2/reqwest/blocking/index.html

2. Iron: https://github.com/iron/iron

There are several web frameworks for Rust: Rocket, Actix, Warp, Iron - but only Actix has released a stable 1.0 release, and there has been considerable controversy over how it uses unsafe Rust.