So, I recently started using
tauri because electron.js was no longer working on my pc... I was amazed to see the release build size of the
It was way smaller than expected.
These are the sized of installers for windows. The project was just a basic
hello worlddisplaying page.
So as you can see,
Tauri is the next desktop framework for webdevs...
Electron.JS is nothing compared to
Tauri by default provides various templates for new projects like
vue.js and a lot more in the future. The
tauri devs are also working on bringing
Tauri depends upon
Microsoft Edge Runtime2 and not bulky core apps like
Electron.JS depends on
Getting started with Tauri
This is for windows only, get your OS instructions on tauri.studio
Microsoft Visual Studio C++ Build ToolsFrom Here
- Finally, Install
This will make your ready for developing in tauri...
For Further Understanding, Check Out The Docs
Top comments (28)
Actually, WebView2 uses the default rendering engine provided by the OS, which on Windows is now chromium (Edge) and on MacOS is webkit (safari). On Linux it will be either webkit or chromium depending on whether you're using Gtk or Qt.
The size of the binary is much smaller with Tauri, but the actual memory footprint while the app is running will be about the same, since (on Windows at least) you're still running chromium to render your app.
That said, Tauri itself is written in Rust and the back-end is likely faster than Electron. It's also simpler for your app to communicate with the back-end with Tauri, in my opinion.
That's what makes the app faster and thats all that matters...
I tend to disagree.
It also comes with a particular disadvantage: You have absolutely NO control over the webengine used to render your application.
Just go back in time a few years, when Internet Explorer was still the default browser on Windows and it powered the WebViews in Windows as well.
Users of Electron apps could enjoy some fantastic modern applications, while Tauri apps (assuming Tauri would've existed back then, of course) would have to limit their functionality to be compatible with Internet Explorer (and/or ship polyfills, yikes!).
While this problem isn't as dramatic as it used to be, there are still some differences between the implemented features in each browser and you as an app developer rely on the OS developers to update their webrendering engine in order to fix (security) bugs, ship new features, etc.
With Electron, you ship the rendering engine by yourself. YOU have the control over the version of the rendering engine you are shipping. What features it has implemented, what bugs are fixes, what security flaws are closed.
Speed is a pretty significant factor, but it's absolutely not the single most important thing.
As in every project you should analyze which technology suits your project the most.
I think Tauri has its place but if it came with an option to always bundle chromium instead of relying on webview then I'd probably choose that option every time.
You mean like electron does? We have gone full circle...
Exactly. I don't have any issue with electron bundling chromium.
But Tauri being in Rust is nicer for the backend.
I agree that still having chromium run like that can be a pain, but wouldn't the reliance on webview mean that multiple apps on tauri would use one instance instead of each one having it embedded into the app?
You save on binary size but remember chromium runs each page in its own process anyway.
I'm actually not sure if parts of the webview renderer are shared. There are obvious security reasons why you might not want this. But if someone knows the finer details of how this works I'd be keen to know.
I'm a huge fan of tauri, having used it recently and found it to mostly just work. It allowed me to write a desktop app in rust without using electron :D
Even if absolutely no runtime state is shared between consumers, the filesystem-backed executable code of the webview is, which also means it's going to end up in cache more often vs running four applications using four separate but barely distinguishable versions of chromium.
Clearly you are just posting a big statement with a big title without basic knowledge of what are you talking about. Stating that this is the next framework just because of saving few megabytes od space is nonsense.
Tauri ships with much less bloat than Electron for a simple Hello World program, but I think it's still too early to say that Tauri will definitely replace Electron. Nonetheless, it's very exciting to see a new alternative to Electron :)
More like throwing a frustration at electron xd,
thats exactly the case cause my pc doesn't work with electeron.js.
NW.js (Similar to electron, provides Source code protection)
DeskGap (bundles a Node.js runtime and leaves the HTML rendering to the operating system‘s webview)
Neutralinojs (chromium module is replaced with either user’s web browser or built-in browser component. Node run-time is replaced with a lightweight web server which exposes native OS functionality)
Proton Native (does the same to desktop that React Native did to mobile, based on github.com/parro-it/libui-node)
React Native Desktop (Cross-platform React Native Desktop port based on Qt framework)
Vuido (creating native desktop applications based on Vue.js, based on github.com/parro-it/libui-node)
NodeGui (powered by Qt5, NodeGui-React, Vue NodeGui, Svelte-NodeGui)
reactxp (library for cross-platform app development using React and React Native)
quasar (Vue.js based framework, which lets web developer to quickly create responsive websites/apps)
Sciter.JS (Is a 5MB HTML/CSS/JS (ES6) runtime aimed as a direct Electron replacement)
Here my problems with Tauri and it is the lack of backend: Tauri doesn't show options for you to build a business layer to manage subservices in your app. Copying a file? Saving a encoded audio from your app based on your configurations? Tauri can't do it. In comparison, electron has a main process that behaves like a backend with communication with your frontend.
I would change to Tauri if it offers a solid robust API for a main process, which don't have.
Couldn't you just code that up in rust and expose it as commands? Isn't that the intended use case? I thought electron changed recently to be more client/server and it became much more strict about communication between the two, for security reasons
That's possible, use the RUST API, just create your functions in rust and invoke them with
You don't need to invoke every command globally
Yeah, i was just giving an example, they have a pretty well documented docs at tauri.studio .
I hope that's part of their road map before hitting 1.0
That still does not solve the main issue for me as a user. That is mainly big memory and CPU footprint of having essentially new browser process for every damn app I need to run.
I know it's maybe easier for the devs and you can have the apps run on Win, Mac and Linux, but the battery life and performance tax is there. And I'm not even talking about electron apps ignoring system preferences like dark mode and having issues to properly interface with peripherals like headsets etc.
that, sadly is true.
But, there are other ways of solving this solution, like building the entire app in languages like C++ or C. This might reduce the CPU usage and memory footprint but for sure is a burden on the developers.
i am very intrested in tauri and have high hopes for it and would like to switch to it, and later with the androida and ios support, the only reason i am reluctant is the fact there isn't a solid backend api, and its complex to setup for beginners web developers, though I am a rust developer so I have the toolchain installed for me.
And because I am a rust developer, i'd personaly use their wry engine, a striped down version of tauri,
if I ever want to build a rust powered app in which I have full control of the application backend.
That's true, it can be very confusing for webdevs to interact with the rust API of tauri. tbh, I am backend dev and I myself found it quite difficult to use the RUST API. But the pro's of
Tauriare they have a great community. The discord community of tauri really helped me a lot.
The setup part will be hard to implement in existing projects, else new projects are pretty fast forward.
The main problem of electron is memory usage and after trying Tauri I realized that it doesn't solve this issue. The webview process that it relies on consumes almost just as much memory usage. Bundle size isn't that big of an issue with people downloading gigabytes of adobe and editing software, most people don't have as big of an issue on that.
With that said, I am yet to find the big selling point of Tauri.
Lol, try Neutralino JS.
Tho Neutralino is currently not mature enough like Tauri or electron, but it has a great potential.
Haha Electron is also slow af....
Nice to meet ya!