rekireki

20 ms·

1.
Benefits of Fullstack Rust(github.com)
1 points by rekireki 9mo ago|1 comments
2.
by rekireki 9mo ago
Let's discuss the benefits of writing fullstack Rust, as well as crossplatform development for Desktop and web targets. What are pros and cons of this approach? I've been using Rust in the browser since early days and noticed a nu
3.
by rekireki 9mo ago
This is cool because it takes a significant effort to implement
4.
by rekireki 9mo ago
It's limited to what NativeActivity / GameActivity can provide. And as @nicoburns mentioned, you'll have to use FFI if you want to access some Android functionality. But it doesn't always go smooth. For example, all my a
5.
by rekireki 9mo ago
One of the reasons for me personally is a rich selection of packages from crates.io. For example if you are writing a server in Rust, and use something like https://crates.io/crates/reqwest for http requests, then you
6.
by rekireki 9mo ago
I've seen it too recently, looks interesting.
7.
by rekireki 9mo ago
I would love to see RustActivity in Android one day, this would make the life much easier.
8.
by rekireki 9mo ago
It doesn't, and I had to write some Java to support clipboard.
9.
by rekireki 9mo ago
How does the text input work there? Does it support IME? Were you able to switch to non-latin keyboards?
10.
by rekireki 9mo ago
Dioxus is WebView, as you've mentioned. Though there's an experimental native renderer mentioned in the README, I would keep an eye on it. And slint should be the same kind of solution as I wrote about. When building native apps f
11.
by rekireki 9mo ago
I left WebView based solutions out of scope. As you can see, I'm focusing on NativeActivity / GameActivity in my post. Though WebView brings you interesting options. For example, iced is inspired by Elm, and with Dioxus you can us
12.
Build Android apps using Rust and Iced(github.com)
173 points by rekireki 9mo ago|85 comments