trust-dns VS tauri

If you don't know what is Trust-DNS / Hickory DNS, this seems to be the repo: https://github.com/bluejekyll/trust-dns

IO is not a part of the async runtime contract (I don't know if this is good or bad), and Tokio & futures famously have different `Async{Read,Write}` traits. I once had to do this [0] to adapt between them.

This means that any crate that uses IO will be bound to a limited number of Runtimes. Everything being Tokio-only is pretty bad (though Tokio itself is great), but here we are...

[0] https://github.com/bluejekyll/trust-dns/pull/1373#issuecomme...

I need a cert.pem and privkey.pem for https://github.com/bluejekyll/trust-dns but even using the extractor to get a cert.pem and privkey.pem from the acme.json file it seems invalid.

You might be interested in Trust DNS - "A Rust based DNS client, server, and Resolver, built to be safe and secure from the ground up."

It looks like you need to reach for a separate crate for that: https://github.com/bluejekyll/trust-dns/blob/7dcb7b983f5407d95d93b800af13caeee975aaa8/crates/async-std-resolver/src/lib.rs

You might be interested in new alternative to dig called dns https://github.com/bluejekyll/trust-dns/blob/main/util/src/dns.rs . I found out about it from https://twitter.com/benj_fry/status/1513269287229657091

I've found the Trust-DNS Resolver crate and it does the job! Now the binary seems to not use any dynamic library to look up the ip of a host.

Tauri is a Rust-based library that enables you to build lightweight desktop applications by leveraging web technologies like HTML, CSS, and JavaScript for the UI. You can use any frontend framework of your choice that compiles to HTML, CSS, and JavaScript. Unlike Electron (a JavaScript desktop app development framework), which relies on Chromium and Node.js, Tauri uses the system's native web view.

Then I learned Tauri and used my favourite frontend framework SolidJS with TailwindCSS and DaisyUI to build the UI with MotionOne to add animations and Tauri to build the desktop/web/android/ios app.

tauri dev is incredibly slow

Are the memory benchmarks measured correctly?

This tauri issue suggests the common measurement approach might be wrong

https://github.com/tauri-apps/tauri/issues/5889

Also would be better to have specific startup time instead of "fast" (which is strange since electron is not known for fast startup)

Here is a whole story: https://github.com/tauri-apps/tauri/discussions/4089

tl;dr - Tauri uses platform's default implementation of a webview. On Windows it's WebView2 which reports back to MS.

I mean, most OSes already ship with a WebView component that you can use instead of shipping an entire browser runtime.

Wails does that: https://wails.io/

Tauri also does that: https://tauri.app/

That does help with the needed resources quite a bit: https://github.com/Elanis/web-to-desktop-framework-compariso...

Sadly it doesn’t change the memory usage much so the technology is still inherently wasteful, but on a certain level it feels like a lost battle - because web technologies often feel like the choice of least resistance when you want GUI software that will run on a bunch of platforms while not being annoying to develop (from the perspective of your run of the mill dev).

HTML/CSS can still be used for the frontend even without Electron. Some frameworks use the OS bundled web renderer instead:

- For Rust apps: https://github.com/tauri-apps/tauri

- For Go apps: https://github.com/wailsapp/wails

Official Website: https://tauri.app/ (v2.0)

In the article, the claim is made: if many popular software products like Slack, VSCode, and Docker Desktop all use Electron, then it must be good.

In response, I would say: while Electron makes it easy for the software developer to build and distribute software, especially on multiple platform, as an end user it is NEVER the best experience.

That's why there are people spending significant effort to develop better solutions than Electron. For instance, the Tauri project ( https://tauri.app/ ) is a lightweight alternative to Electron.

The article defends the minimum application bundle size of 100MB-300MB is as no issue, because streaming 4K video takes much more bandwidth than such a software download. But the bigger issue than disk space or download bandwidth is the RAM usage and overall low performance of Electron projects. Even with a 16 GB or 32 GB RAM system, when you're running many apps and doing serious multitasking, the gigabytes quickly get used up and then things slow down.

For example, if you have used VSCode, try using the Zed editor (https://zed.dev/). You will be blown away by its incredible speed. Launches in the blink of an eye, and it responds to every input with zero latency. We have forgotten that software can actually be fast.

Jonathan Blow, "Will Software Stop Getting Slower?" https://www.youtube.com/watch?v=4ka549NNdDk