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

Tauri: Rust-based Electron alternative releases beta

tauri.studio

Post reply on HN
Print view View original

121–130 of 177 posts

Re: Tauri: Rust-based Electron alternative releases beta

#121

Post by [deleted] »

capableweb wrote: post #87
bstar77 wrote: post #85

Earlier quoted context omitted.

"Tauri is a toolkit that helps developers make applications for the major desktop platforms - using virtually any frontend framework in existence. The core is built with Rust and the CLI leverages Node.js making Tauri a genuinely polyglot approach to creating and maintaining great apps." That's the first paragraph on the About page. Landing pages have multiple purposes and need to address different types of viewers,…

> The marketing speak is likely more for convincing IT manages this is a legit project and does not have common "deal breakers". If this is the case, it's an excellent reason to not use Tauri. Making their decisions based on what IT managers want to read rather than what developers need to do their job? Good luck with that, might work in some bubbles but the rest of the world is trying to be productive.

[deleted]

Re: Tauri: Rust-based Electron alternative releases beta

#122

Post by jeremyjh »

bstar77 wrote: post #85
andrewmcwatters wrote: post #42

I don't care about your YouTube videos, I don't care about your governance, I don't care about your book, tell me what it is in non-marketing speak and show me a screenshot on the front page and shut up about everything else. Tell me what it is, show me what it looks like, provide a "Hello, World!" API example for opening a window on the front page. Stop contributing to landing pages that jerk the consumer around.

"Tauri is a toolkit that helps developers make applications for the major desktop platforms - using virtually any frontend framework in existence. The core is built with Rust and the CLI leverages Node.js making Tauri a genuinely polyglot approach to creating and maintaining great apps." That's the first paragraph on the About page. Landing pages have multiple purposes and need to address different types of viewers,…

They are nowhere near ready for pitching IT managers. The only thing that matters right now is winning developer interest.

Re: Tauri: Rust-based Electron alternative releases beta

#123

Post by parker-codes »

Please keep in mind that this project just reached _beta_. We are working to implement valuable feedback from the community, so please don't expect things like the landing page to be as polished as an 8 year old project.

Shout out to all of the hardworking people behind Tauri. ♥

Re: Tauri: Rust-based Electron alternative releases beta

#125

Post by nklayman »

stdgy wrote: post #97

So what are the benefits to using Tauri over Electron? Are app sizes smaller? Is the memory footprint smaller?

Yes, much smaller install size and memory footprint. We have a comparison table on our readme: https://github.com/tauri-apps/tauri#comparison-between-tauri...

Re: Tauri: Rust-based Electron alternative releases beta

#126

Post by mikepurvis »

irq-1 wrote: post #77
andrewmcwatters wrote: post #42

I don't care about your YouTube videos, I don't care about your governance, I don't care about your book, tell me what it is in non-marketing speak and show me a screenshot on the front page and shut up about everything else. Tell me what it is, show me what it looks like, provide a "Hello, World!" API example for opening a window on the front page. Stop contributing to landing pages that jerk the consumer around.

It's a webview wrapper. > ...the Tauri-team incubated and maintained WRY, which creates a unified interface to the system webview (and other goodies like Menu and Taskbar), leveraging WebKit on macOS, WebView2 on Windows and WebKitGTK on Linux. https://github.com/tauri-apps/tauri

Doesn't using the "system" webview throw out the main selling point of Electron, which is that you're shipping the browser, so you no longer need to support more than one of them?

Re: Tauri: Rust-based Electron alternative releases beta

#127

Post by fabiospampinato »

gilrain wrote: post #107
fabiospampinato wrote: post #93

Earlier quoted context omitted.

> Order of magnitude memory reduction That doesn't make sense to me, you are still using a browser at the end of the day. Sure you can save some memory by not bundling Node (at the cost of making even reading a file much more difficult), but that's not orders of magnitudes.

Now it's a browser that was probably already in memory for one reason or another, not necessarily a process per Tauri app.

That's a good point, that will save you some memory unless you happen to be in a scenario where for example you use Chrome under macOS and a single Tauri app, which would then use Safari under the hood, meaning still multiple browsers.

But I think that would save much less memory than people think. A bare-bones hello-world Electron app consumes about ~100MB of RAM (rough figure since it depends on many factors), maybe you can bring that down to ~20MB by sharing a common browser instance (I doubt it, a Chrome tab takes like ~50MB for me right now), but if your app uses 1GB+ of memory that has way more to do with how the app is coded than by having to spawn another instance of the browser. Basically you won't get a memory hungry app consuming 10x less memory by running it as a website.

Re: Tauri: Rust-based Electron alternative releases beta

#128

Post by nsonha »

fabiospampinato wrote: post #68

As a developer of an Electron app to me a competing framework that doesn't bundle its own rendering engine doesn't make sense, why would I want to trade control over how my app is rendered for ~100MB of disk space? I might as well just ship a website at that point, almost everything that makes Electron appealing comes from shipping your own rendering engine.

And most people have problem eith Electron's ram usage, which I don't think this addresses. No one really cares about 100mb

Re: Tauri: Rust-based Electron alternative releases beta

#129

Post by nklayman »

Thaxll wrote: post #41
iudqnolq wrote: post #12

Earlier quoted context omitted.

They use whatever is the system WebView on the platform you run the code on. On Windows that's the Edge engine, on MacOS it's Safari's engine, etc. Those are all some combination of C and C++. See https://github.com/tauri-apps/wry Edit: s/IE or Edge/Edge

So you need to make sure your code works on 3 different platform eventhough you're using a tool that's supposed to fix that problem in the first place? I don't know the extend of WebView in Electron is it something common?

A ton of time and resources have been put into making web apps work across multiple rendering engines. These days, it can be difficult to have something break on one platform if you are using a modern development stack. The webview engines that Tauri uses are all quite modern, see https://github.com/tauri-apps/wry/discussions/202 for more details.

Re: Tauri: Rust-based Electron alternative releases beta

#130

Post by danudey »

mikepurvis wrote: post #126
irq-1 wrote: post #77

Earlier quoted context omitted.

It's a webview wrapper. > ...the Tauri-team incubated and maintained WRY, which creates a unified interface to the system webview (and other goodies like Menu and Taskbar), leveraging WebKit on macOS, WebView2 on Windows and WebKitGTK on Linux. https://github.com/tauri-apps/tauri

Doesn't using the "system" webview throw out the main selling point of Electron, which is that you're shipping the browser, so you no longer need to support more than one of them?

Perhaps, but using the system webview also means that you don't have massive amounts of bloat, both in distribution and on-disk size as well as memory usage, and you have a better chance at getting better performance.

Besides, all of the relevant engines are WebKit variants, so you're not targeting Trident or Gecko or anything.

Bear in mind that a lot of popular "apps", like Slack, Discord, etc., are web apps anyway, so there's a decent chance that the "support more than one of them" problem is already solved anyway, meaning you don't have to spend any more development time but you get huge increases in performance and responsiveness.

Post reply on HN