Electron vs. Tauri

Arrowmaster 3 hours ago | parent | next [-]

The author has obviously never tried Tauri on Linux. I've never seen one of their AppImages work correctly. Every project uses the upstream GitHub action to build binaries and it compiles dynamically linked binaries limited to the glibc from the Ubuntu 22 or 24 VM used. Xdg-open is often broken too from broken environment variables in the AppImages, so you can open a link in the default web browser. The entire build process needs reworked.

	▲	andai 7 minutes ago \| parent \| next [-]
		I've been a lifelong Linux user, and this makes me sad. I don't know enough to comment about whether or not it's necessary, but any time I've tried to get anything working that wasn't updated recently, it was impossible. Well impossible is a bit strong, the process ranges from: - Find a forum post that links to some old .deb files and install them manually - Install a newer version of a dependency and then recompile from source code, after spending an hour or two updating the program so it works with the new version of the dependency because the dependency changed its API for no reason (that one's not a Linux problem per se, but it wouldn't be necessary if the old one still worked!) Better to download the Windows version and run it in WINE...
	▲	dfabulich an hour ago \| parent \| prev \| next [-]
		It's like they always say: Win32 is the only stable ABI on Linux.
	▲	ambicapter 22 minutes ago \| parent \| prev \| next [-]
		Sadly, every time that one guy posts his personal finance app on HN I try it and every time tauri gives me trouble to build, and when I fix whatever build errors it gives me it basically opens up a blank window and the app doesn't work (He now offers a Docker image which I can't help but feel is related to these difficulties).
	▲	WhyNotHugo 2 hours ago \| parent \| prev [-]
		The idea of AppImages is neat, but the implementation is awful and rarely works (except perhaps on Ubuntu and Fedora and extremely similar scenarios). The main issue being that they're dynamically linked binaries, which is exactly what you want to avoid for their use case. Using packages from your favourite distribution is usually your best bet.

▲

dfabulich 7 hours ago | parent | prev | next [-]

> Lack of support for .appx and .msix bundles on Windows

https://github.com/tauri-apps/tauri/issues/4818

Whoa, I had no idea about that. Tauri is way less fully baked than I realized.

The bug goes on to explain that Tauri apps can't have Windows "package identity", which means that there's a bunch of Windows APIs you simply can't use in Tauri, including the notifications API.

Without package identity, IMO, Tauri isn't ready for primetime on Windows.

▲

01HNNWZ0MV43FF 7 hours ago | parent [-]

Huh, I thought I'd seen notifications and app URI handlers in a Tauri app. Maybe they were using a custom Wix builder and not the Tauri template though.

	▲	TingPing 3 hours ago \| parent [-]
		Yes it should be doable manually, not like this is a complex feature.

▲

sundarurfriend 7 hours ago | parent | prev | next [-]

> As you’d expect, this makes Tauri apps far more lightweight.

Note that lightweight compared to Electron does not mean it's actually lightweight. In my experience, Tauri apps are still pretty heavy and a constant drain on system resources; maybe they're 2x better (faster/lighter) compared to an Electron equivalent, but they're still at least 10x worse compared to native apps.

With a Tauri-based app (just like with Electron), I have to constantly remember to close the app at the soonest possible point in time, or I can tangibly feel the sluggishness it creates in the system performance. So if there's a native choice and a Tauri-written choice, I'd heavily prefer the native choice nowadays, even at the cost of some features.

▲

quinncom 6 hours ago | parent | next [-]

I'm curious what the impact on system resources is between a Tauri-based app versus the web app version opened in a browser window. If the features for both are the same, I imagine the resource utilization is also the same. The only exception might be that browsers such as Chrome will force inactive tabs to sleep.

Readwise Reader is one app I've compared both versions to, and I don't see much difference in resource usage for either version.

▲

galleywest200 6 hours ago | parent | prev | next [-]

Last time I messed with Tauri my bin folder in my code/building directory ballooned to 10 gigs. If the final product is “lightweight” the development process surely is not.

	▲	aabhay 5 hours ago \| parent [-]
		That’s just Rust in general. But what you lose in disk space you gain considerably in optimized executables. The tradeoff is well worth it.

▲

01HNNWZ0MV43FF 2 hours ago | parent | prev [-]

Hm, that shouldn't happen. It does use RAM for the web view, but an idle Tauri app won't use CPU any more than any other idle app or web browser tab.

▲

mootoday an hour ago | parent | prev | next [-]

My personal favorite to keep an eye on is https://www.gpui.rs/.

It's what Zed(.dev) is based on. While not quite ready for prime time from what I understand, if Zed is the reference implementation, I'm sold!

	▲	brainless an hour ago \| parent [-]
		This was recently on HN and I think it adds so much value to GPUI: https://github.com/longbridge/gpui-component/

▲

WhyNotHugo 2 hours ago | parent | prev | next [-]

I tried using Tauri a few weeks back, and the build system is an absolute nightmare.

I gave up after a few hours. The last issue I encountered was it trying to link udev and libinput. libinput is a library for writing compositors, and their website literally state "libinput is not used directly by applications". I've no idea why Tauri was trying to link this (and some rough ideas of why it wasn't working due to the absence of udev on that host), but at this point, I didn't care any more.

▲

kristianp 4 hours ago | parent | prev | next [-]

How does Wails compare here? I'm guessing it's less mature than Tauri.

	▲	TACIXAT 3 hours ago \| parent [-]
		My current project uses Wails and a previous one used Tauri. I like Tauri a bit more but not enough to justify porting Go code to Rust. The primary difference I run into is how the JS <-> native interface is exposed, but this is very minor. Tauri is much slower to build, I think this is just the nature of Rust though. Stats here. [1] 1. https://github.com/Elanis/web-to-desktop-framework-compariso...

▲

anon115 3 hours ago | parent | prev | next [-]

i had a better time vibe coding with gpt 4 with WAILS> vs any of these Electron> Tauri

	▲	pylotlight 2 hours ago \| parent [-]
		Go is likely much easier to work with here than the other platforms imo

▲

aabhay 7 hours ago | parent | prev [-]

If they didn’t have the nodejs dependency then the Tauri bundle could be as small as 20mb.

Another pro not mentioned is that native integrations (i.e. obj-c on macos) are much easier to do since rust has great ffi integration with other native libraries.

The biggest pro to electron is that it has extensive plugins that are often widely used in production by large companies. But Tauri is definitely winning and any new project should use Tauri no matter what essentially.