What do you get from this you cannot get from building your app in QT, Flutter, or Lazarus?
Probably the "written in rust" label.
Tauri – Electron alternative written in Rust
201–210 of 435 posts
Re: Tauri – Electron alternative written in Rust
#202Earlier quoted context omitted.
>"It enables someone to build something where previously they could build nothing. It makes getting from 0 to 1 that much easier." Making GUI apps using Electron tech for front end is no less time consuming than doing GUI in Lazarus for example. But the end result is way more frugal in the latter case.
> Making GUI apps using Electron tech for front end is no less time consuming than doing GUI in Lazarus for example It is a lot faster if you already know web tech stack, and you would have to learn Lazarus/pascal
And since you have to know the web stack to exist at all on browsers that box is checked for basically everyone. Break the dominance on the DOM and JS in browsers and you open the door to better cross-platform toolkits.
Re: Tauri – Electron alternative written in Rust
#203Earlier quoted context omitted.
They call it rust, because everything written in it becomes derelict after 180days of its first 3 'written in rust' posts
Let's put this meme to bed. Tauri has been developed for two years now. People don't just write Rust because it's trendy. If you want to throw stones at Rust, there are many more substantial criticisms to make. Our compilation times are long. Those sweet, ergonomic macro interfaces are only possible because of proc-macro dark magic that tends to be very verbose and special case-y. There's no spec. Unsafe is overused.…
And where are GATs ?
(See also: https://blog.rust-lang.org/2021/08/03/GATs-stabilization-pus...)
Re: Tauri – Electron alternative written in Rust
#204Imagine trying to use app built with this in five to ten years that not recently updated or maintained, very scary.
Care to elaborate why that would be more problematic than any other app that hasn't been updated or maintained in that period of time?
Not the op but, giving this rely in whatever is on the host OS, the DLL's on the host OS will evolve changing its interface or even not ship anymore while with applications that rely the bare minimum like electron this is not a issue.
Re: Tauri – Electron alternative written in Rust
#205Here's a similar, older and slightly less hipster project for Go, C, C++ (and more languages via C-API bindings): https://github.com/webview/webview ...I wouldn't go as far as calling a simple WebView widget wrapper an "Electron alternative" though.
According to the About page of Tauri, the Tauri team is maintaining the Rust bindings of Webview.
Source: https://tauri.studio/en/docs/about/intro#polyglots-not-silos
Re: Tauri – Electron alternative written in Rust
#206Earlier quoted context omitted.
"cross-platform compatibility" isn't guaranteed on the web either, yet somehow "cross-platform compatible" websites exist. It isn't a problem that's so difficult it requires wrapping a 60Mb runtime around every individual app instance.
Most cross compatibility issues have been resolved in browsers. Firefox and Chrome are pretty much at parity, Edge is chrome and Safari is the exception. Web views are less standardized though and require more finesse.
> Firefox and Chrome are pretty much at parity, Edge is chrome and Safari is the exception.
Firefox and Safari are very much at parity. Chrome ships ~40-70 new "standard" APIs every month or so: https://web-confluence.appspot.com/#!/confluence
Re: Tauri – Electron alternative written in Rust
#207I have a hard time understanding why platforms like electron are so popular. The predictions from Gary Bernhardt seem to really be true, in the future everything will be javascript. I wonder if somebody actually tried to make an OS that only has a browser, that's what Chrome OS actually is, after all.
We built our product for the web. People wanted our product as a desktop app. So we wrapped it in Electron and now we have 3 desktop apps. People wanted our product as a mobile app. So we wrapped it in Capacitor and now we have two mobile apps. There are just two of us building this product.
So efficient for you, but 1000x more resources everywhere it runs.
I wonder if someone can quantify the carbon impact of Electron just from Slack.
Re: Tauri – Electron alternative written in Rust
#208Earlier quoted context omitted.
JS DX always seemed really quite bad whenever I looked. A constantly shifting landscape of frameworks and packages where nothing will stand for long before being eroded away.
let's see - language: ES / Typescript are quite established - CSS: also quite established - Frameworks: there is still a lot of innovation here, but also React / Vue / Angular are quite established. on that latter part I prefer the innovation. Let's just imagine for a while what UI would look like if we only had Swing (Java) or QT (C++)
> Let's just imagine for a while what UI would look like if we only had Swing (Java) or QT (C++)
yes, Telegram looks so bad right ?
Re: Tauri – Electron alternative written in Rust
#209Is "written in Rust" a registered trademark already?
good question
Re: Tauri – Electron alternative written in Rust
#210Earlier quoted context omitted.
Sorry but requiring web devs to ignore the last 4~5 years of progress is just unacceptable. Not that that would fix the situation, there are still rendering inconsistencies between browsers when using stuff like margins floats and tables.
Then do as I: develop in Firefox and if it works there (and isn't a PWA where maybe you get in trouble with Safari?) then it works everywhere. Less testing, less bugs. Whats not to like? Contrast to Chrome first developers who often get caught by cross browsers incompatibilities just like they did back in the days when they were IE first developers : )
> Contrast to Chrome first developers who often get caught by cross browsers incompatibilities just like they did back in the days when they were IE first developers : )
I'm not entirely sure how I feel about this statement (and comparison to IE). If anything, Safari is "the new IE" rather than Chrome.
MOST (hopefully the nitpickers pick up the caps lock) stuff in Chrome are drafts or standards.
Sure, Google pioneered/championed some of them, but that's kinda irrelevant if developers voted for those features. There's very little Chrome-specific stuff.
Also, other browsers have vendor specific stuff in them too, yet people rarely fling shit in their direction?
FWIW I also mostly use Firefox for dev because I prefer how some devtool features are designed/implemented.
Most of my cross browser issues in FF were "brief" in the senses that they were bugs that got fixed eventual.