Live data from Hacker News

Tauri: An Electron alternative written in Rust

tauri.studio

171–180 of 438 posts

Re: Tauri: An Electron alternative written in Rust

#172

Looks like it uses system webviews instead of bundling a copy of Chromium? This to me seems like the real headlining feature, but strangely I had to dig pretty deep to find it: https://tauri.studio/en/docs/getting-started/technical-detai... I kind of wonder why it took this long for someone to try this approach. It just makes a whole lot more sense on the surface. Interesting thing I just thought about: since users d…

[deleted]

Re: Tauri: An Electron alternative written in Rust

#174

Can we just stop using browsers as a framework for desktop applications? That's not what they are meant for. Electron and everything like it is the ultimate expression of developer laziness.

Can we stop attributing technology choices to laziness? Sounds like a _lazy_ evaluation and presumption of someone else's motivations.

More seriously, there are far more folks familiar with browser frontend technologies than the myriad of desktop frameworks, rife with their own challenges.

Re: Tauri: An Electron alternative written in Rust

#175

Looks like it uses system webviews instead of bundling a copy of Chromium? This to me seems like the real headlining feature, but strangely I had to dig pretty deep to find it: https://tauri.studio/en/docs/getting-started/technical-detai... I kind of wonder why it took this long for someone to try this approach. It just makes a whole lot more sense on the surface. Interesting thing I just thought about: since users d…

I think my best-case scenario would be an Electron replacement that is not so bloated and also keeps parts of Firefox well-funded and people looking at compatibility.

Elevating a new stack is a good consolation prize.

Re: Tauri: An Electron alternative written in Rust

#176

Earlier quoted context omitted.

I supposed you're being sarcastic. The realistic version of this is that we have experience and evidence that tells us that it has the potential to be more performant.

So does the assembly version I just started work on.

Oh shoot! If only the industry realized sooner that everything ultimately compiles to Assembly and thus decades of PL research were utterly useless! We were wrong about this the whole time. How could we not realize? We better off rewrite everything in Assembly to squeeze out every clock cycle!

Re: Tauri: An Electron alternative written in Rust

#177

Earlier quoted context omitted.

> Front-end developers have to test against Chrome, Firefox, and Safari, at a minimum. Do many companies actually do this though? I've only ever been with companies that test against Chrome. The one time at FF bug was found, that company told that client to switch to Chrome. I know there was a kerfuffle about Airbnb and Groupon only doing Chrome as well. https://www.reddit.com/r/AirBnB/comments/dv7v6n/customer_sup...…

Yes, absolutely. Every company that I've ever worked at had a list of officially supported browsers that included Chrome, FireFox, Safari and Edge/IE. QA engineers would make sure to rotate through various browsers while testing, and for crucial features would run through every scenario in every supported browser's oldest and newest supported versions.

Pretty much the only reason to use Saucelabs is browser compatibility testing.

We don't run everything through it, but we run karma to make sure the code runs and the right events fire. It is still possible to write code that runs everywhere but IE.

Re: Tauri: An Electron alternative written in Rust

#179

Earlier quoted context omitted.

That is not how it works on Windows, as you have to ship either the Webview2 runtime or installer with your app - otherwise you’re stuck with the old rendering engines. At which point, it’s just easier to ship Electron.

Shipping Electron and bundling the WebView2 runtime are practically the same level of difficulty. Making an installer is not that hard, and you should have enough respect for your users' compute resources to go through the modicum of effort it takes.

>Making an installer is not that hard, and you should have enough respect for your users' compute resources to go through the modicum of effort it takes.

No. As shown by the slew of other comments in this thread, it's not just about getting the runtime to load. You still have other issues involved.

You should have enough respect for your own time and money to ship the product and not open yourself up to a litany of cross-platform issues. Your job is not to fix OS vendors failing to get a common UI framework in place.

Signed, someone who has literally dealt with cross-platform-webviews in a shipping product in the past six months, and who builds native Mac apps.

Re: Tauri: An Electron alternative written in Rust

#180
post #27

Whenever I'm reminded of Electron, I'm thankful to have experienced WinAmp!

ironic, because Electron apps should be easily skinnable. just put new CSS and images, maybe some new html, especially if there's some way of exposing e.g. the UI components so you can alter the layout and such.

I used to use an Electron wrapper for Google Play Music (may it rest in peace) and the developer of that did this. The default colour scheme for that product was a harsh orange, but the Electron client allowed you to override the CSS to change that base color, as well as switch between light/dark mode.
Post reply on HN