Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tauri 2.0 Release Candidate

v2.tauri.app

Post reply on HN
Print view View original

31–40 of 101 posts

Re: Tauri 2.0 Release Candidate

#31

Post by sirwhinesalot »

traveler1 wrote: post #22
ktosobcy wrote: post #20

Earlier quoted context omitted.

Sadly instead of having native apps we have "web" monstrosities... each sporting custom "fancy" UI instead of following the OS native style…

Because WinUI and QT are so glamorous and offer a super intuitive development experience. /s

Best part is that neither of those follows the "native style" either. There's no dark uxtheme provided by windows, so Qt falls back to their fusion style. Even the "native" light theme doesn't follow the new "fluent" style so that's also a shitshow.

As for WinUI 3, apps are supposed to bundle it, so if you target Windows 11 and run the app on Windows 10, it'll look all rounded and drop-shadowy instead of flat like native Windows 10 apps. Great stuff.

Re: Tauri 2.0 Release Candidate

#32

Post by cute_boi »

pdpi wrote: post #4
kayson wrote: post #2

I've been following tauri for a bit. It seems very cool and interesting but I've always wondered - what are the use cases for putting your app in a webview instead of using the browser? Everything I've thought of would work just as well.

The goal is to make a standalone desktop app with access to local resources, so the question is "why should you put your app in a webview instead of Electron or a native toolkit?" The answer is that Electron forces you to carry a whole Chrome installation around, which is unnecessarily heavy, and (AIUI) you have a node.js backend giving you the means to touch the actual OS, whereas Tauri lets you write Rust (YMMV as…

Additionally, we don't have to package whole node js thing.

Re: Tauri 2.0 Release Candidate

#33

Post by Sytten »

We just finished migrating away from Tauri to Electron for our desktop application after running Tauri for 2 years. We are a rust shop so it makes sense to use Tauri, but I can't recommend it for a startup use until they allow packaging a webview into your build. The amount of time you currently have to spend in debugging each OS/Version combination of bugs is simply untenable. This is scheduled for v3 last time I talked to the devs.

Otherwise good progress, happy to see it!

Re: Tauri 2.0 Release Candidate

#34

Post by dvt »

Sytten wrote: post #33

We just finished migrating away from Tauri to Electron for our desktop application after running Tauri for 2 years. We are a rust shop so it makes sense to use Tauri, but I can't recommend it for a startup use until they allow packaging a webview into your build. The amount of time you currently have to spend in debugging each OS/Version combination of bugs is simply untenable. This is scheduled for v3 last time I ta…

I also use Tauri for a startup project I'm getting off the ground and I've been extremely impressed. Unless you're doing something extremely non-standard, I'm not sure what edge cases you're seeing. The webviews packaged with modern operating systems are very compliant (essentially Safari on MacOS and Chrome on Windows). The only wildcard is Linux which uses WebKitGTK which does have all kinds of weird quirks (but that's a comparably tiny market sector to begin with).

Using OS WebViews, you also get the added bonus of security updates which you get for "free" with OS updates (otherwise you have to handle these yourself). There have been some RCE exploits in Electron, so it's something you need to keep an eye out for.

Re: Tauri 2.0 Release Candidate

#35

Post by lovethevoid »

Sytten wrote: post #33

We just finished migrating away from Tauri to Electron for our desktop application after running Tauri for 2 years. We are a rust shop so it makes sense to use Tauri, but I can't recommend it for a startup use until they allow packaging a webview into your build. The amount of time you currently have to spend in debugging each OS/Version combination of bugs is simply untenable. This is scheduled for v3 last time I ta…

Have you or your team written about the migration? Would love to read about that more as usually there's a lot to learn from these situations even when you don't make the same move.

Re: Tauri 2.0 Release Candidate

#36

Post by Sytten »

lovethevoid wrote: post #35
Sytten wrote: post #33

We just finished migrating away from Tauri to Electron for our desktop application after running Tauri for 2 years. We are a rust shop so it makes sense to use Tauri, but I can't recommend it for a startup use until they allow packaging a webview into your build. The amount of time you currently have to spend in debugging each OS/Version combination of bugs is simply untenable. This is scheduled for v3 last time I ta…

Have you or your team written about the migration? Would love to read about that more as usually there's a lot to learn from these situations even when you don't make the same move.

We might do it, I don't necessarily want to push bad publicity on Tauri since I want them to succeed in the end :)

Re: Tauri 2.0 Release Candidate

#37

Post by Sytten »

dvt wrote: post #34
Sytten wrote: post #33

We just finished migrating away from Tauri to Electron for our desktop application after running Tauri for 2 years. We are a rust shop so it makes sense to use Tauri, but I can't recommend it for a startup use until they allow packaging a webview into your build. The amount of time you currently have to spend in debugging each OS/Version combination of bugs is simply untenable. This is scheduled for v3 last time I ta…

I also use Tauri for a startup project I'm getting off the ground and I've been extremely impressed. Unless you're doing something extremely non-standard, I'm not sure what edge cases you're seeing. The webviews packaged with modern operating systems are very compliant (essentially Safari on MacOS and Chrome on Windows). The only wildcard is Linux which uses WebKitGTK which does have all kinds of weird quirks (but th…

Yup this was also our first impression. Wait until you have users (no snark here, but its the reality). We do have around 1/3 of our users on Linux and WebKitGTK is plainly bad.

Our application is complex I will give you that, but it isnt just that. Say you want to use WASM you have to check which macos versions you want to support and check the oldest possible webview (it doesn't get updated at the same time as safari), check which subset of WASM that supported, etc. It really is a nightmare of subtitle bugs that are hard and time consuming to reproduce.

OS webviews in our findings have a way worse update cycle than us shipping a new version of the app.

Re: Tauri 2.0 Release Candidate

#38

Post by theultdev »

dvt wrote: post #34
Sytten wrote: post #33

We just finished migrating away from Tauri to Electron for our desktop application after running Tauri for 2 years. We are a rust shop so it makes sense to use Tauri, but I can't recommend it for a startup use until they allow packaging a webview into your build. The amount of time you currently have to spend in debugging each OS/Version combination of bugs is simply untenable. This is scheduled for v3 last time I ta…

I also use Tauri for a startup project I'm getting off the ground and I've been extremely impressed. Unless you're doing something extremely non-standard, I'm not sure what edge cases you're seeing. The webviews packaged with modern operating systems are very compliant (essentially Safari on MacOS and Chrome on Windows). The only wildcard is Linux which uses WebKitGTK which does have all kinds of weird quirks (but th…

I've ran into this trying to use OPFS with Tauri. While it works in Safari 17, it's unavailable in 16 for many users.

There's also various UX differences in webviews.

It's all fine though, I'd rather have multiple webviews over a bloated app. Used to developing for multiple environments anyways.

Re: Tauri 2.0 Release Candidate

#40

Post by lovethevoid »

Sytten wrote: post #36
lovethevoid wrote: post #35

Earlier quoted context omitted.

Have you or your team written about the migration? Would love to read about that more as usually there's a lot to learn from these situations even when you don't make the same move.

We might do it, I don't necessarily want to push bad publicity on Tauri since I want them to succeed in the end :)

That's very understandable. It can be hard to get people to grasp that it's not a versus competition when these migrations happen, it's all about the compromises (and that's where the fun reading is for me, selfishly!)
Post reply on HN