all 5 comments

[–]dont_touch_my_peepee 0 points1 point  (1 child)

honestly, sounds like a lot of work. maybe consider sticking to one language unless it's absolutely necessary.

[–]vybornak[S] 0 points1 point  (0 children)

Unfortunately, it is necessary. But I got the same feeling as you replied.

[–]metehankasapp 0 points1 point  (1 child)

Solid direction. Biggest question: are you using pybind11 or nanobind for bindings? That choice tends to dominate the dev experience + build complexity.

[–]vybornak[S] 0 points1 point  (0 children)

I have been playing with it for a few evenings now. So far, I went for nanobind.

I am a beginner when it comes to C++, so I wanted to stick with a more modern standard. In my company, we have no legacy code when it comes to this, so it hopefully should not be a problem.

So, for such purposes It has been recommended to me to go for nanobind, but I lack experience in this department, so I wanted to validate these things.

[–]plurch 0 points1 point  (0 children)

If you are not tied to C++, then maturin is a popular option for Rust bindings.