pilka VS rust-socketio

Github: https://github.com/pudnax/pilka

Still Ash or Erupt. Erupt exploits builder pattern more often than ash which saves you from annoying bugs 'temporary variable have been dropped, but only in release mode' like this https://github.com/pudnax/pilka/commit/2860f3d538a1b16e4ce64c7b589feae320ddc750 .

I'm trying to capture sound from the microphone using cpal and apply FFT on it. The reason is I want to pass sound into shader as 1D texture. pilka

Working on a little demotool for personal usage. Implemented shader hot-reloading and now thinking about FFT and how to store result with the textures https://github.com/pudnax/pilka

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.