Why I chose Tauri, and what it cost me
A developer shares six months of experience building Tabularis, a cross-platform database client, using Tauri instead of Electron or native frameworks. The core argument: a database client is a systems program, so having a real Rust backend (SQLx, Tokio, keyring, SSH tunnels) matters more than bundle size. The post honestly catalogs the real costs of Tauri's shared-webview model — targeting three different webview implementations (WKWebView, WebKitGTK, WebView2), Linux packaging nightmares (AppImage ballooning to 94 MB, glibc compatibility floors, Wayland bugs), and the IPC serialization tax on every query result. The conclusion is nuanced: Tauri is the right choice when the application is genuinely systems-heavy and needs a rich cross-platform UI, but anyone describing it as a free lunch hasn't shipped an AppImage to enough Linux users.