Live data from Hacker News

Tauri 2.0 Release Candidate

v2.tauri.app

71–80 of 101 posts

Re: Tauri 2.0 Release Candidate

#71
post #69

I’ve been using Tauri for an app I’m developing. The Tauri team is super helpful in their Discord channel. Writing everything in Rust, including the UI (using Axum) has been nice. I’m really excited for 2.0 and mobile support! My app (very beta) https://meshly.cloud

Very cool! Is a Linux version coming?

It's not high on my TODO list for the project, but shouldn't be too much work. I'd give it a try if you're interested. Want me to reply to your comment when I get a Linux version released?

Re: Tauri 2.0 Release Candidate

#72

Earlier quoted context omitted.

Nothing says "private mesh app" like signing up for an account.

Thanks for the feedback. I use the accounts to know which device want to be connected. The devices create a mesh network via webrtc. Perhaps, I need to make it more clear why accounts are needed.

Or you could generate device IDs/QR codes for pairing, a la Syncthing.

Re: Tauri 2.0 Release Candidate

#73

Earlier quoted context omitted.

Thanks for the feedback. I use the accounts to know which device want to be connected. The devices create a mesh network via webrtc. Perhaps, I need to make it more clear why accounts are needed.

Or you could generate device IDs/QR codes for pairing, a la Syncthing.

QR codes would be a great addition. I've even tested out sending the WebRTC offer/answer via a QR GIF (due QR image data limits) to make the connection very private. The account solution was quick to setup for now and allowed me to easily test the network conditions with peers across the US (I'm in Iowa). A QR code solution or some other solution that makes it super simple to connect devices is definitely a priority for the future.

Re: Tauri 2.0 Release Candidate

#74
post #19
post #17

Earlier quoted context omitted.

I clicked “Get started…” and saw this: > What is Tauri? > Tauri is a framework for building tiny, fast binaries for all major desktop and mobile platforms. Developers can integrate any frontend framework that compiles to HTML, JavaScript, and CSS for building their user experience while leveraging languages such as Rust, Swift, and Kotlin for backend logic when needed. This ought to be on the front page.

Yeah for sure. Personally I wouldn't click 'Get started...' on anything unless I already know what I'm getting started with and why.

That'll show 'em!

Re: Tauri 2.0 Release Candidate

#75
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…

Exactly my own experience. I like rust and I like the package size. But if I was to build this again I would 100% go with electron.

They started working on 2.0 with the docs for v1 in a 10% state. I mostly searched through discord threads for tidbits. It was painful.

Expect the documentation for 2.0 to be at 5% for years.

Re: Tauri 2.0 Release Candidate

#76
I am curious, I work for a company that has a bunch of hardware(serial communication) that communicates to our modules is built via python. So all the backend tooling is python that has the drivers and quality of life functions to support that hardware. Would love to make a native experience instead of a webapp (flask etc)

Does anyone have a solution to this? Would love to use Tauri as a desktop server and create the WebView. But do I just use ffi for every single class/module/function?

Or does anyone know a more elegant solution to bridge the gap of making a native desktop experience while still leveraging the years of python drivers that have been built up

Re: Tauri 2.0 Release Candidate

#77

One big difference between tauri and electron is that tauri can deliver to mobile, from my understanding. Is there an hybrid way to deliver with tauri on macos and windows, but electron in linux?

It would be cool if there was a system where linux users could install one version of Chromium that is kept up to date on their distro, and Tauri would check if that is available first and somehow use that as the webview, otherwise falling back to whatever the system ships. So you could have multiple Tauri apps that all use the same Chromium under-the-hood (this also has benefits that security is maintained better, a…

I wonder if electron could be used for that purpose. It's effectively chromium in a digestible webview format. Having an always up to date electron would be useful for various reasons

Re: Tauri 2.0 Release Candidate

#78

One big difference between tauri and electron is that tauri can deliver to mobile, from my understanding. Is there an hybrid way to deliver with tauri on macos and windows, but electron in linux?

Any reason why? Tauri works fine on Linux as I understand.

Webkitgtk is a source of problems. If tauri could address that, it would become my go-to for app building.

Re: Tauri 2.0 Release Candidate

#80

Earlier quoted context omitted.

I don't have any understanding why that would be though. Even if it is true, is there a reason or is it happenstance / path-dependence? It seems so inferior to have the same thing but lose access to the browser's suite of tools/capabilities. What could possibly change other people's opinion or what should I use to reconsider my perspective?

When it comes to a non-hosted web app most non-technical users would have no concept or ability to run a local web server whereas “install this app” is something they’re familiar with. I’m talking from a position of “I have an app that I want to distribute to a population of end users.” If that population happens to be technical your solution would likely work fine. As well if you’re not distributing apps to end user…

> When it comes to a non-hosted web app most non-technical users would have no concept or ability to run a local web server whereas “install this app” is something they’re familiar with.

Clearly not true.

Sonarr and Radarr for example installs like a normal app. Then sits in the system tray. If click the system tray, most options inside launch a web browser that brings you to the localhost webapp. https://sonarr.tv/

People seem to assume this would be a hard to handle thing, but you can easily applicationize your local web services. And your local web service daemon can expose things like a system tray, to afford some classic manageability.

Post reply on HN