I only have one question. Was the name inspired by Stargate?
This was my first thought as well.
Tauri: An Electron alternative written in Rust
231–240 of 438 posts
Re: Tauri: An Electron alternative written in Rust
#232Earlier quoted context omitted.
> A major benefit of Electron is that you can develop against a single browser version and don't have to deal with all the small but time consuming compatibility quirks. Somehow I doubt the ideal solution is to bundle a web browser with every app. Electron feels like a prototype that went out of control.
I think they're overstating the browser compatibility problem too. It was really bad 15 years ago, but today it is almost a non-issue. Between significantly improved standardization of web technologies, and new tricks like polyfills, I think it has become pretty uncommon for apps to not just work on multiple browsers without any tinkering.
"almost a non-issue" doesn't sound very convincing to me.
As someone who doesn't write GUIs often, I just don't want to have to worry about it at all. What's the cost of electron over webviews? 100mb hdd space? On the other side of the trade, never having to worry about cross platform concerns again? Not having to support or test on multiple platforms?
Seems like a no brainer to me. But it's entirely possible, even likely, that I'm putting too much faith in electron, or that there are better options I just don't know about.
Re: Tauri: An Electron alternative written in Rust
#233I think the desktop seriously needs a production, RAM and developer friendly breakthrough that isn't Electron. Tauri may be it, but the desktop SO needs this moment, I don't want to see 50 years on and Electron is still being used.
There's React Native for Windows/macOS, though if you don't like Electron I doubt that's very appealing either.
I've had some nice experiences using PyInstaller to create desktop apps.
Re: Tauri: An Electron alternative written in Rust
#234Earlier quoted context omitted.
Dynamically loaded system libraries use shared memory. You can load it once for the entire system.
That's what I mean by executable code. But that is only really minor (<100MB or so) compared to the remaining resource usage.
Ah, sorry, I missed that in your comment.
Re: Tauri: An Electron alternative written in Rust
#235"The core is built with Rust and the CLI leverages Node.js"
Sublime to the gorblimy in one sentence!
Re: Tauri: An Electron alternative written in Rust
#236Earlier quoted context omitted.
Some corporations did that. Most didn't. The main reason IE dominated was that most people didn't care, and stuck with the default. The main reason old versions of browsers were more common than new ones was that self-updating browsers hadn't become a thing yet, and most people didn't care, and just stuck with the default. The reason most browsers stay up-to-date now is that modern browsers are all configured to self…
My experience was that IE finally got bad enough (around version 8), and Chrome got good enough, that even "grandmothers" started having everyone telling them to use Chrome, and it was so incredibly superior that you didn't have to be technical to appreciate it. Now the reason everyone uses it is because it's psychologically the new "default", whether it is on the actual system or not. Everybody knows that's just wha…
> most people don't bother to re-evaluate that default assumption that "the windows browser is bad"
That's one way to look at it.
Another way is to say that Microsoft has lost customer's trust and now has to work extra hard to earn it back.
IMO they've learned their lesson, at least for now, but it would also be great if others could learn from Microsoft's mistake too.
Re: Tauri: An Electron alternative written in Rust
#237If someone paid me to do something similar, I would probably be building on top of this: https://github.com/Const-me/Vrmac There’re two hard problems there. One is how to render vector graphics and fonts. So far, only web browsers do that in a cross-platform way. Windows has it’s Direct2D and DirectWrite, while Linux has nothing comparable, unfortunately. Another higher level one is how to build easy to use GUI libra…
Why not just wrap/abstract the native platform APIs (like what wxWidgets does)?
Re: Tauri: An Electron alternative written in Rust
#238Earlier quoted context omitted.
As a developer shipping executables to MacOS, Windows, and Linux today this is the only assumption I can make. I cannot assume that dependencies exist or are the correct version, I can't assume the user knows that package managers exist or that the dependencies shipped by the package managers are correct, I can't assume anything exists on PATH or LD_LIBRARY_PATH, and I can't even assume that libc or libc++ on a syste…
It isn't your fault that you have to do this, it is that our industry hasn't created enough quality, easy to use, cross platform gui libraries for popular languages, such that the only viable place to turn is to use a whole web browser.
I don't think this is entirely true.
Have you tried wxWidgets or even Qt?
In my experience, this is more about resources and economics ("reuse existing code" vs. having to learn something new).
Re: Tauri: An Electron alternative written in Rust
#239Earlier quoted context omitted.
Isn’t that what this is basically?
Is it? I couldn't find it.
https://tauri.studio/en/docs/getting-started/technical-detai...
"The first generation user interface in Tauri apps leverages Cocoa/WebKit on macOS, gtk-webkit2 on Linux and Webkit via EdgeHTML / Chakra on Windows. Tauri leverages the MIT licensed work known as webview that has been incorporated into the officiall webview_rust bindings."
Re: Tauri: An Electron alternative written in Rust
#240Question: Why do we need Electron alternatives? Why do we need to develop applications that need a bundled browser to run? Why can't we just use GTK/Qt?
There is a lot of effort currently being put into creating web applications. It would be nice if we could use the fruits of that labor on desktop and mobile applications. That's how I understand it, anyway.
It would also be nice if people understood and really appreciated the trade-offs of doing so – i.e. hogging resources, killing batteries, potentially wrecking the end users' experience and ability to multitask efficiently, etc.