serde-this-or-that VS gtk-rs

GitHub | crates.io | Changelog

I was just working over the weekend on putting together a project, serde-this-or-that which is inspired by a blog post of a similar name, even though technically that blog post appears to discuss something slightly tangential to the matter. This project is inspired by a question posted on SO, which suggested a crate might be useful to deserialize cases where a json field has one of multiple possible multiple types (for example it could come as str or bool). I was also working on adding benchmarks, which this is actually the first crate where I have successfully put together benchmarks using criterion which I've been kind of nervous about using in general, but based on the docs it was pretty easy to set up so I'm kind of glad about that at least.

Update: for those curious, I've added benchmarks for comparison with serde_with here. After some more testing, I've release v0.4 and am confident that performance is now on par with serde_with. Also, I noticed that whenever serde_with::PickFirst is used, performance drops; in this case, serde_this_or_that does seem to perform 12x better in such scenarios.

The full release notes can be found on the project page on GitHub as well.

I've just published an initial release of serde-this-or-that, which builts on top of serde to provide custom deserialization for fields that can be specified as multiple types.

gtk-rs

GTK: I have little - no experience with GTK, and from what i have read it is cross-platform similar to wxWidgets, however is an emulated UI system similar to Qt. As i have no experience with it i am not sure how well supported this library is as far as it's Rust - bindings are concerned gtk-rs

In a gtk-rs application, I'm running a xdotool command to get the id of the application's window. I'm running the command in a connect_show closure (after the window has been shown):

To build the UI, I used gtk-rs. My experience with this library was quite pleasant; it was easy to use and there were a lot of examples. However, it isn't as widely used as, say, React, so it was difficult to find answer on Stack Overflow (I come from a JavaScript/Typescript background).

I'm using x11rb to interact with a window created with gtk-rs. window_id is the ID of the window created with gtk-rs. window_id_2 is the ID of the window created with x11rb (for testing purposes).

I haven't used it yet, but gtk-rs looks pretty good too. I've used GTK in general, just not the Rust bindings so far. The tutorials seem nice and GTK is a good UI toolkit overall.

I'm using gtk-rs. I want to trigger some code after the window has been shown (has displayed on the screen):

I'm using gtk-rs to add ListBoxRow items to a ListBox. The items are successfully added if I do it outside of input.connect_changed, a closure. But nothing is added if I do it from inside input.connect_changed:

For GTK, there's https://gtk-rs.org/

Out there there are already some open source projects trying to do this, but most of them are abandoned or in a very alpha stage. The most promising project so far seems to me git-kt. This project is trying to do something similar to what gtk-rs does for Rust, which is using GObject Introspection (GIR) files to generate Kotlin native bindings automatically.