Earlier quoted context omitted.
Kind of but also not. Tauri uses the default on the platform it runs on, this zig-webui project seems to be able to use every major browser and every major platform. For example, Firefox, Chrome and Edge all seem to be available for Windows, Linux and macOS in zig-webui, while Tauri would use a specific engine for a specific platform (by default at least).
Tauri can use a separate browser runtime if required. The use default is a space saving mechanism.
Tauri has problem on Linux, webkit2gtk has lower performance etc. I know I have problems with three.js, others with svg
Additionaly communication speed between backend and frontend is bottleneck (serialisation to string) and you must use custom protocols to effectively communicate/send large data, zero copy binary protocol isn't possible at the moment