wry

Is there any webview control ready to use in linux? When I say Tauri it's just the webview control, used as a cargo package as "wry" in macos. I don't care about the framework itself, just the webview control. If that's the case then Rust/(stripped down WebView) is all we need to be honest Edit: Looks like the same "wry" package can be used in linux https://github.com/tauri-apps/wry

I thought so too at first. It is definitely something interfaced on top of Tauri[0] with some sort of 'server-side logic' framework[1]. But looking at Tauri's site, it is really hard to disentangle if PyWry is a binder about WRY[2] or not. "OS-efficient cross-platform HTML-based UI toolkit" is a great technological thing, but neither PyWry and Tauri's sites make that clear, or meaningfully advertise what they do. Which is a shame, because there is myriad software which might benefit all to use this. [0] Tauri is akin to Chromium, I think? https://tauri.app [1] and also a rather large amount of LLM integration; the source for PyWry has a whole section for Claude bindings [2] the Webview Rendering librarY (WRY) used in Tauri https://github.com/tauri-apps/wry

Yup, came here to say this. After reading the article, it became abundantly clear that the author doesn’t support Linux and most of the article is just a summary of the common Tauri talking points that are out of date. To add data to this - Tauri is looking to allow embedding chromium as an option because the creator of Tauri acknowledged that it doesn’t work well on Linux. To the point where if Linux is a serious target, they don’t recommend Tauri: https://github.com/tauri-apps/wry/issues/1064#issuecomment-2... The upstream projects aren’t in a place to support this yet so this feature didn’t make it into Tauri v2. I’ve been tracking this for a long time and hope that they will make it possible in v3.

In my experience with Tauri, it's pretty good on Windows, but not so much on other platforms, especially Linux. The decision to target different browser engines on each operating system means you still have to deal with a bunch of different OS-specific bugs. For Windows you're dealing with Edge (so Chromium), on macOS you have Safari, and on Linux you have WebKitGTK. WebKitGTK has honestly abysmal performance, and you're missing a lot of modern standards. The Tauri devs are looking at bundling a Chromium browser with it to deal with that, but that's still some time off, and leads to the same issue Electron has, where you have large bloated applications. https://github.com/tauri-apps/wry/issues/1064

Wait - there's system webviews? On Mac, Windows, and Linux? Edit: It looks like Tauri uses the following platform webview features. https://github.com/tauri-apps/wry?tab=readme-ov-file#platfor...

Optionally bundling would help in situations where the OS's native webview has degraded performance https://github.com/tauri-apps/wry/issues/1064

Costa here, one of Hopp builders. We chose to go native with Rust instead of just using the screen-sharing provided from Webkit for a few reasons: 1. Granular access to OS APIs. For example on MacOS you can select applications that you want to exclude from screen-sharing, which we know we want to use in the future. https://developer.apple.com/documentation/screencapturekit/c... 2. Being able to tweak the WebRTC client. In our case we patch libwebrtc for minor bugs, and tweak parameters to allow lower latency in video streaming 3. This: https://github.com/tauri-apps/wry/issues/85

Yeah, Tauri would be great. But I think it will take quite some time until the fundamental rendering performance issues [1] under Linux can be fixed. There seem to be rough plans to bundle CEF on Linux [2], but AFAICS this seems to be only a discussion at this point. [1] https://github.com/tauri-apps/tauri/issues/3988 [2] https://github.com/tauri-apps/wry/issues/1064

Nice! There is also Servo webview for Qt: https://github.com/KDABLabs/cxx-qt-servo-webview and Servo webview for Tauri: https://github.com/tauri-apps/wry/tree/servo-wry-demo Hopefully we can get more web browsers with embedded Servo engine (e.g. as a QtWebEngine replacement).

Sometimes you do just want to use off-the-shelf libraries for things and not need to re-implement them yourself. If you already have a web app you’re building around, it’s annoying to need to rewrite bits of it - especially rock solid 3rd party libraries - unnecessarily. Another consideration is that any webview<->native bridge is going to impose some kind of bridge toll in the form of serialization and message passing (memcopy) overhead. You can call into WASM from JS synchronously, and share memory between JS and WASM without copying. Sync calls from webview to Tauri native code doesn’t appear to be possible according to https://github.com/tauri-apps/wry/issues/454 Finally, security posture of native code running in the main process is quite different from WASM code in the webview. I maintain a WASM build of QuickJS and I would never

tauri-apps/tauri: https://github.com/tauri-apps/tauri : > The user interface in Tauri apps currently leverages tao as a window handling library on macOS, Windows, Linux, Android and iOS. To render your application, Tauri uses WRY, a library which provides a unified interface to the system webview, leveraging WKWebView on macOS & iOS, WebView2 on Windows, WebKitGTK on Linux and Android System WebView on Android. ... Tauri GitHub action: https://tauri.app/v1/guides/building/cross-platform/#tauri-g... WebView: https://en.wikipedia.org/wiki/WebView CEF: Chromium Embedded Framework > External Projects: https://github.com/chromiumembedded/cef#external-projects : cefglue, cefpython,: https://github.com/cztomczak/cefpython (edit) tauri-apps/wry > Bundle Chromium Renderer; Chromium WebView like WebView2 (Edge (Chromium)) https://github.com/tauri-

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...

https://github.com/tauri-apps/wry This rocks, especially with some IPC between the "native" things like filesystem + TCP sockets -> JavaScript "bridge".