nothingismagick

@wravery and co had some great insights about this (with specific regard to WebView2) on twitter a while back. Maybe we could collate those here in a lead-up to a...

In light of the feedback from the 3.0 release's approach of removing several popular projects, we should address this now and find a way to tackle this from several approaches:...

This is a really exciting challenge, and I wonder if the initial bottleneck would be the different codesigners...

One of the (only?) concerns with rustler Nifs is that you won't be able to handle extreme crashes... https://news.ycombinator.com/item?id=31023587

A neat use case for this would be to ship an elixir binary as a sidecar and use phoenix channels and websocket listeners in the webview (or just place liveviews...

Liveview is really AFAIK SSR HTML passed to Tauri via websockets. So you HAVE to place the liveview into the webview somehow and that means integrating a websocket.

But we haven't experimented with how you would interact with the API in this way, but it is interesting for sure.

So I guess there might be several ways to do this. One abstract method would be to craft a `cardscript-to-i18n` package, which would have the advantage of being “presentation” agnostic,...

Thankyou for the report!

Closing this because we now are releasing android/ios support in the next branch (2.0.0-alpha). See this merge: https://github.com/tauri-apps/tauri/pull/5787/commits/df2e027dd97b9cab7cbe350b40bde9bea31d05fe