pilka VS ash

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

If you want to automate the creation of certain code that will be nested under the src directory, and committed into source control, there are a variety of ways to do that. One option is to create a sub-crate in your project that does the code-gen and you can run it as needed. The ash project is an example of this.

There is also [Vulkano](https://github.com/vulkano-rs/vulkano). It has a safe high level api and lower level layers, all the way down to [ash](https://github.com/ash-rs/ash) which is more or less raw vulkan. It's more explicit and verbose than [wgpu](https://github.com/gfx-rs/wgpu) though, so maybe try wgpu first and see how you like it.

This is great, of all the vulkan go bindings I have been waiting for one that uses vk.xml to generate the bindings, because it's the only viable way to keep the bindings up-to-date. (fyi the popular [ash-rs](https://github.com/ash-rs/ash) is created the same-way).

Nice and simple. Its quite portable too. But simplicity and ease of use come with some limitations. Ash is much more complex but can extract every bit of power from your card if needed. Wgpu-rs github comes with many examples and you can find a really nice tutorial here

low level vulkan bindings

Glium and ash provide low level access to different common graphics api's. I'm sure there's a good directx-11/12 bindings as well but I'm unfamiliar with what people use.

This project was inspired by the Bonzomatic, KodeLife and others, as well as in educational purposes to learn Vulkan using ash.

The closest thing to vulkan afaik is literally vulkan bindings, iirc I've seen the ash (https://github.com/MaikKlein/ash) crate recommended for that, but that is fairly unsafe.

I would not recommend vulkano, I would recommend ash, most serious projects that are targeting only vulkan (ie not using gfx-hal), use ash. Vulkano makes some odd decisions and their build process is a pain, if it works in c++, you might not be able to get it to work in Vulkano. Ash has the same exact dependencies you would need in a C++ rust project (ie just the vulkan sdk on windows), and most low level conversion stuff to rust (enums) is already done.