gattii VS rust-socketio

I've started working on a rewrite of my Gattii serial terminal UI (https://gitlab.com/susurrus/gattii) to rely on libhandy so it's usable on the Librem 5, which I'm planning to purchase when they to GA this year. I've been wanting to rewrite it for a while since there's some longstanding bugs around parsing data and even how the GUI is implemented since gtk3 used a lot of OO style architecture. Gtk4 is more about composition and I think will map a lot better to Rust than Gtk3 does. So I'm working on a demo application with all dummy data to get a sense of how it'll work in an adaptive interface but still be usable on a desktop.

The world has moved on though to opinionated tools, and Rust isn't even the furthest in that direction (That would be Go). The equivalent of those two lines in Cargo.toml would be this example of a basic configuration from the jacoco-maven-plugin: https://www.jacoco.org/jacoco/trunk/doc/examples/build/pom.x... - That's 40 lines in the section to do the "defaults".

Yes, you could add a load of config for files to include/exclude from coverage and so on, but the idea that that's a norm is way more common in Java projects than other languages. Like here's some example Cargo.toml files from complicated Rust projects:

Servo: https://github.com/servo/servo/blob/main/Cargo.toml

rust-gdext: https://github.com/godot-rust/gdext/blob/master/godot-core/C...

ripgrep: https://github.com/BurntSushi/ripgrep/blob/master/Cargo.toml

socketio: https://github.com/1c3t3a/rust-socketio/blob/main/socketio/C...

Looks great! Was the motivation for creating this better integration with Tower? How does it compare to https://github.com/1c3t3a/rust-socketio . I haven't used either, but I was thinking about using the latter in an upcoming project. Now I am considering using this one.

So I set out to write a Socket.IO server by extending the existing crate rust-socketio.

I‘m working on the implementation of a socketio client in rust. https://github.com/1c3t3a/rust-socketio.