Should I migrate to wails from my custom alternative?

[samuelgozi]

I've been developing an app for about a year, and over that time I migrated from Tauri to my custom solution.
The main reason I left Tauri was because developing in Rust is very slow, and the communication with "sidecars" is not convenient.

After being force to learn Go, I loved it, and I refactored big parts of my app to Go gradually (after proving it was easier to maintain and had better performance in my very specific case). But then I still had the barrier of inter process communication, which involved serialization, dependencies, and glue code with Rust.

So I decided do the only reasonable thing, write my own alternative. It went as you would expect, a big pain in the butt. But at the end it works fine (only on mac).

I'm thinking about switching to Wails because I think that in the long run, the ecosystem will improve, and catching up in my own solution will take too much time from working on the business logic, which is not a good idea when you are developing something alone.

I would like to know how Wails handles the following cases, which will help me decide whether to move (or when):

• Does wails start a local server in production? Tauri, and my solution work with Vite's server only on dev, and in production we use "custom scheme handling" (available in Webkit) which is a direct interface. This is preferred for security and performance reasons.
• Which serialization protocol does Wails use when transferring data across Go-C-Webkit boundaries? Does it use JSON, or similar, or is it a custom/low level protocol? This is important to me because I transfer (potentially) hundreds of MBs per second between them, so I developed a custom protocol that does less copies, and weighs less.
• Does Wails use Reflection on runtime to determine how to serialize the shared data?

Thanks for the amazing project 🙏