One of the major challenges of Tauri is that it doesn't guarantee a consistent, or even eventually-consistent degree of API support.
An immediate example of this is WebGPU access. If Tauri ran Chromium everywhere, an app could use WebGPU on most desktops that will support it's current version, either right now, or very soon.
Because Tauri uses the default browser, the release date for a Linux app using GPU compute is "soon-ish?" and Mac is "ehhhhh". And because it goes with what is on the path, there is no accounting for version, either.
Iād really like there to be a dynamic installer process that allowed you to check for certain requirements and then check for other browsers, and then install a different head, as a last resort. No WebGPU in Safari? Is Chrome installed? Go with that. No? Then let me install a portable version that this Tauri app and all others can use.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
One of the major challenges of Tauri is that it doesn't guarantee a consistent, or even eventually-consistent degree of API support.
An immediate example of this is WebGPU access. If Tauri ran Chromium everywhere, an app could use WebGPU on most desktops that will support it's current version, either right now, or very soon.
Because Tauri uses the default browser, the release date for a Linux app using GPU compute is "soon-ish?" and Mac is "ehhhhh". And because it goes with what is on the path, there is no accounting for version, either.
Iād really like there to be a dynamic installer process that allowed you to check for certain requirements and then check for other browsers, and then install a different head, as a last resort. No WebGPU in Safari? Is Chrome installed? Go with that. No? Then let me install a portable version that this Tauri app and all others can use.