Show HN: Async UI: A Rust UI Library Where Everything is a Future
11–20 of 96 posts
Re: Show HN: Async UI: A Rust UI Library Where Everything is a Future
#12Re: Show HN: Async UI: A Rust UI Library Where Everything is a Future
#13Fly you fools. This will be a nightmare to debug, introspect and reason about for a speed boost that you (and your users) won’t be able to measure.
If you want to build a native app, more power to you. There are simpler languages that will enable you to do that with a much higher productivity.
Kudos to the library writer though!
Re: Show HN: Async UI: A Rust UI Library Where Everything is a Future
#14The login form example which returns values reminds me a lot of imgui and other immediate mode GUI frameworks.
Re: Show HN: Async UI: A Rust UI Library Where Everything is a Future
#15So, does this work with an application that uses tokio?
But can you share more on what you need Tokio for? I'd completely understand if we're working with servers. But when it come to clients - UI applications - I feel like async-std and smol are pretty competitive.
Re: Show HN: Async UI: A Rust UI Library Where Everything is a Future
#16You might be interested in RUI https://github.com/audulus/rui
The cool thing is this: with some effort, it is probably possible to adapt the two library together to have a UI with RUI's rendering system and Async UI's APIs.
Re: Show HN: Async UI: A Rust UI Library Where Everything is a Future
#17I don't understand the motivation about lifetimes in sync rust not being able to be arbitrary. I'm also confused because most of the time went you want to send data around in a async context you wrap it in `arc`, which has the pretty much analogous `rc` in a sync context which would also solve the lifetimes issue. Is there something I am missing?
Re: Show HN: Async UI: A Rust UI Library Where Everything is a Future
#18So, does this work with an application that uses tokio?
This uses the executor used by async-std rather than the one used by Tokio. So if you're using something Tokio-specific, you would probably need async-compat[1]. But can you share more on what you need Tokio for? I'd completely understand if we're working with servers. But when it come to clients - UI applications - I feel like async-std and smol are pretty competitive. [1]: https://docs.rs/async-compat/
Because everything. uses. Tokio. It's become the defacto standard of async Rust, whether people like it or not.
This issue has been notable enough to cause some projects to outright consider dropping async-std support - and I think they only relented because there's apparently enough (private, not-open-source) users who apparently still use it.
(https://github.com/launchbadge/sqlx/issues/1669)
(Note that they also have a note about async-compat not exactly being an ideal solution and that they'd be looking into writing their own)
Re: Show HN: Async UI: A Rust UI Library Where Everything is a Future
#19I'm not sure the complexity of doing everything using async constructs is worth it, though. Large-scale UI's built in Qt or Javascript are mostly single threaded anyway, but it's still worthwhile to explore so kudos for that. Looking forward to seeing how far you get.