mogwai VS rs_pbrt

Thanks for taking the time to read this! Please let me know here or at the repo (or on any of the other channels you may find me) if you have any concerns, bugs, feature requests, etc.

I’ve been working on the 0.6 release of mogwai, which is a library for building GUI views. This release is all about making the library domain agnostic, meaning it can be used to define views in any GUI domain (ie browser, native, gtk, wgpu game). I’m also trying to trim down the API and improve the RSX macro.

Here's a link to Mogwai: https://github.com/schell/mogwai - its Github readme also has other benchmark numbers (also from TodoMVC but with newer versions of Mogwai) that shows it faster than Preact and Mithril.

I solved the SSR problem in my library mogwai using conditional compilation to include an encoding of the DOM element when compiled for non-wasm targets, which you can see here). The extra field ServerNode allows me to provide an html_string function on non-wasm targets. On wasm targets the html_string function is backed by the DOM element's outerHtml method.

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.