6 ms·

The same can be said of Electron.

• YorickPeterse 5y ago
  The difference is that Electron guarantees you're always using a known version/engine. With Tauri, you'd be using whatever is installed, and that engine may behave different from what you are used to. So basically you get all the drawbacks of developing for different web browsers, without really any of the benefits a cross-platform GUI gives you.
  • wila 5y ago
    Just like building for the web then? In that scenario you also do not know what version the browser is (or even what kind of browser). An advantage would be that the browser gets security patches by the OS.
  • imbnwa 5y ago
    Is this really a problem now that IE11 is finally being deprecated? You basically have Blink/Gecko/Webkit which is no different from regular web dev
  • jokethrowaway 5y ago
    Does it use less RAM because it's shared with the system browser? I sure as hell avoid all the Electron based apps because of their memory consumption. Cross-browser compatibility is not too bad these days.
    • YorickPeterse 5y ago
      I did some testing using webview (https://github.com/Boscop/web-view https://github.com/Boscop/web-view) which is used by Tauri if I'm not mistaken. On Linux this uses webkitgtk, and it used a total of around 100 MB. That's not that good, but certainly better compared to Electron.