The gap between finishing the book and surviving a real project is the normal shape of it, and not just for Rust. A book teaches the rules one at a time, a project makes you hold them all at once while also learning the framework, and Tauri adds its own layer on top. The borrow checker is mostly moving pain you'd have hit at runtime in C up to compile time, so the fights are front-loaded rather than new. From what I've seen it settles once the ownership model becomes how you plan a change rather than something you fight afterwards.