wry VS mtr

The biggest benefits we derived from Tauri were Wry and the sidecar mechanism. Wry (the second half of Tauri: tao/wry) is a cross-platform WebView rendering library in Rust that supports all major desktop platforms like Windows, macOS, and Linux. It essentially spins up a native web view from whatever operating system it’s running on and doesn’t require an application to bundle one with it. Wry greatly reduces the overhead of “pushing” a browser to our users, instead leaning on the host OS to handle rendering a web view. This made our applications really lean.

Check out https://tauri.app/ - specifically, https://github.com/tauri-apps/wry, which provides a cross-platform interface to the system's WebView.

Tauri uses WebkitGTK, which has pretty bad performance compared to other browsers on the same hardware.

https://github.com/tauri-apps/wry/issues/890#issuecomment-14...

One small note regarding Native Webview meant above. You can find ultimate information on this topic here. In a nutshell, Tauri applications use as HTML renderer Webkit (safari engine) on MacOS, Microsoft Edge WebView2 on Windows, and WebKitGTK on Linux (port of Webkit for Linux). Pay attention to the fact that a Tauri application could behave differently on different platforms according to the information above.

wry looks like a better choice, but no one has bothered to work on this task, yet.

I think this might be somewhat close to what you're looking for: https://github.com/tauri-apps/wry

They're wrapping the Android webkit/webview stuff in wry and creating an activity for it. I imagine they've already achieved or are close to achieving full parity API-wise to proper Tauri desktop apps.

Another way to approach it is to wrap the web app in a webview and use Tauri for custom logic, see https://github.com/tauri-apps/wry. You'd need to teach yourself some Rust though. I'm sure you could achieve something similar with Express. The performance will be similar to using a browser so not terrible.

It uses the WebView that the underlying OS provides to render the application’s UI — this is one of the reasons why the application binaries are smaller (as compared to electron). The WRY library from the Tauri toolkit provides a unified interface to interact with WebViews provided by different operating systems. The WRY library uses the Tao crate for cross-platform window management.

As a reminder, Trippy combines the functionality of traceroute and ping and is designed to assist with the analysis of networking issues. You can think of it as a modern, cross platform, Rust based version of tools such as mtr, with a bunch of advanced features and a fancy TUI.

Cool project! Two suggestions, one serious, one frivolous:

- I wonder if you could get more accurate results by using TCP or UDP instead of ICMP. I think traditional traceroute has an option to use UDP, mtr [1] can use TCP or UDP, and tcptraceroute [2] can use TCP.

- This would be a perfect fit for some Talking Heads references. "And you may ask yourself, well, how did I get here?" [3]

[1] https://github.com/traviscross/mtr

[2] https://linux.die.net/man/1/tcptraceroute

[3] https://en.wikipedia.org/wiki/Once_in_a_Lifetime_(Talking_He...

Run mtr, or whatever the Windows equivalent might be, and leave it running shortly before 4:15pm, and see where the traffic stops when the Internet shuts off.

Lot of great stuff here, haven’t seen MTR yet: https://github.com/traviscross/mtr

Consider using MTR (software) towards the actual end-point of the SIP connection to get a combination of traceroute and ping which will be much more revealing. This will also allow you to quickly identify if the problem is local to your equipment or somewhere along the path. Consider allowing her to join a Google Conference from Teams to determine if it is provider related. Yes, port mirroring and wire shark is the gold standard and will display the "answer" on your screen quickly but it requires skills to know what to analyze, look at and how to interpret the data.

Have you tried something like mtr to check for connection issues? I would recommand the view you get when hitting d twice after starting it (with the colored graph for latencies).

Continuing to build trippy; a network diagnostic tool inspired by mtr. There is still a long way to go but it is getting closer to feature parity with mtr.