pilka VS chromiumoxide

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

Re rust-headless-chrome: yes, being handwritten it probably has a nicer API/DX but is missing some features. I would give it a go if you are struggling with chromiumoxide. The flakoness could be due to chromiumoxide going faster than the browser, ie trying to get elements before they have loaded. Most web automation tools will have ways to slow down themselves down, eg wait for 1 second, or keep checking whether an element exists. This is what things like Playwright provide, not sure what chomiumoxide does. Also not sure if this is something that is part of the devtools spec and thus should already be in chomiumoxide, or features implemented on top, in which case chomiumoxide might not have it (though I suspect it probably does) eg see https://github.com/mattsse/chromiumoxide/issues/42 In hindsight chomiumoxide might not be the best choice for you if it is lacking these kinds of features. I'm just using it for executing Javascript, not acually interacting with the Dom. I prefer it because I think the codegen approach is best and is the project most likely to succeed long term.

Adding a ton of new features for the headless chrome api chromiumoxide, especially javascript evaluation functions. Also started implementing a test suite.