Tauri – Electron alternative written in Rust
tauri.studio
Tauri – Electron alternative written in Rust
1–10 of 435 posts
Re: Tauri – Electron alternative written in Rust
#2Re: Tauri – Electron alternative written in Rust
#3> [leverages] WebKit on macOS, WebView2 on Windows and WebKitGTK on Linux.
So cross-platform compatibility isn't guaranteed, unlike Electron.
Re: Tauri – Electron alternative written in Rust
#4If anyone wants to know how it works: > [leverages] WebKit on macOS, WebView2 on Windows and WebKitGTK on Linux. So cross-platform compatibility isn't guaranteed, unlike Electron. https://github.com/tauri-apps/tauri
Re: Tauri – Electron alternative written in Rust
#5Re: Tauri – Electron alternative written in Rust
#6If anyone wants to know how it works: > [leverages] WebKit on macOS, WebView2 on Windows and WebKitGTK on Linux. So cross-platform compatibility isn't guaranteed, unlike Electron. https://github.com/tauri-apps/tauri
It isn't a problem that's so difficult it requires wrapping a 60Mb runtime around every individual app instance.
Re: Tauri – Electron alternative written in Rust
#7This seems to be a good fit. I guess when you can reduce the api calls to bindings (accessing filesystem, network, etc.) cross platform compatibility should not be a problem.
Re: Tauri – Electron alternative written in Rust
#8If anyone wants to know how it works: > [leverages] WebKit on macOS, WebView2 on Windows and WebKitGTK on Linux. So cross-platform compatibility isn't guaranteed, unlike Electron. https://github.com/tauri-apps/tauri
"cross-platform compatibility" isn't guaranteed on the web either, yet somehow "cross-platform compatible" websites exist. It isn't a problem that's so difficult it requires wrapping a 60Mb runtime around every individual app instance.
Re: Tauri – Electron alternative written in Rust
#9Earlier quoted context omitted.
"cross-platform compatibility" isn't guaranteed on the web either, yet somehow "cross-platform compatible" websites exist. It isn't a problem that's so difficult it requires wrapping a 60Mb runtime around every individual app instance.
Everyone is basically using Chrome or Safari nowadays - so WebKit. Very little incompatibilities to consider compared to writing something that works on different WebView implementations