rs_pbrt VS tauri

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.

Hi, dear Tauri! Long time no see. I published my first post, Developing a Desktop Application via Rust and NextJS. The Tauri Way almost a year ago. Since then, Tauri has become stronger. I'm happy about that! And now, I am very pleased to make a useful contribution to the Tauri community. As a full-stack developer, I frequently face situations where I need to start a DB-based UI project as fast as possible. It's stressful if I need to start the project from 100% scratch. I prefer to keep some boilerplates on hand, which will save me time and nerves and will be the subject of this article.

Hey Thanks!

Just electron & vite. I might actually migrate off electron, Tauri (https://tauri.app/) seems to be getting more stable and it's gotten great reviews.

I think this is the boilerplate I used though https://github.com/cawa-93/vite-electron-builder.

Well the great thing about WebAssembly is that you can port QT or anything else to be at a layer below -- thanks to WebAssembly Interface Types[0] and the Component Model specification that works underneath that.

To over-simplify, the Component Model manages language interop, and WIT constrains the boundaries with interfaces.

IMO the problem here is defining a 90% solution for most window, tab, button, etc management, then building embeddings in QT, Flutter/Skia, and other lower level engines. Getting a good cross-platform way of doing data passing, triggering re-renders, serializing window state is probably the meat of the interesting work.

On top of that, you really need great UX. This is normally where projects fall short -- why should I use this solution instead of something like Tauri[2] which is excellent or Electron?

[0]: https://github.com/WebAssembly/component-model/blob/main/des...

[1]: https://github.com/WebAssembly/component-model/blob/main/des...

[2]: https://tauri.app/

Welcome to the 2nd episode of our series “Building with Tauri”, where we chat with developers who build amazing projects and products using Tauri.

Tauri seemed like the "thing" I should switch to because everybody loves Rust (heh), and because it ships significantly smaller apps.

First of all, I will be using npm as my package manager but feel free to use whatever you prefer. Find more info here.

Today I'm talking about Tauri! Do you know all the various tools that allow you to develop native applications starting from web languages? They often need an intermediate compilation, in the middle of which you end up encountering various problems not always transparent and directly solvable with a language mostly detached from native development. On the other hand, there's still the ease of developing attractive and easily usable interfaces, which are more difficult to develop with low level languages.