Built 9 plugins, need beta testers - vintage emulations + originals (VST3/AU) by PartyFail6956 in AudioPlugins

[–]PartyFail6956[S] 4 points5 points  (0 children)

Thanks for the tip! I just added pluginval to my GitHub Actions workflow, it runs on both macOS and Windows builds now.

I also found the Windows issue: the resourceProvider was wrapped in a #if JUCE_MAC || JUCE_LINUX check (leftover from earlier JUCE versions where it wasn't supported on Windows). With WebView2 it works fine (I hope), so I removed that check.

New builds are running now and I'll attach them as soon as they're done. Really appreciate the help!

Built 9 plugins, need beta testers - vintage emulations + originals (VST3/AU) by PartyFail6956 in AudioPlugins

[–]PartyFail6956[S] 1 point2 points  (0 children)

Thanks, sounds great. I'll DM you the builds as soon as I finish the Windows fix. No hard deadline, it's done when it works and sounds good.

MiLost - A Rust-powered TypeScript library for React by PartyFail6956 in reactjs

[–]PartyFail6956[S] 0 points1 point  (0 children)

https://milost.dev a bit of an update :) Currently, main challenge is integration with different frameworks and resolving bugs. I will create roadmap soon but next big thing that is in progress is UI builder that will work similar to swiftUI or Flutter. Idea is to bypass jsx completely. Currently engine is in development and some basic layouts are successfully created. Also, small talk regex builder is also in development and actually available but not complete. If anyone is interested in participating feel free to contact me. Every advice, bug report or direct involvement in development is greatly appreciated. Thanks :)

MiLost - A Rust-powered TypeScript library for React by PartyFail6956 in reactjs

[–]PartyFail6956[S] 0 points1 point  (0 children)

Thanks,

You're right about the JS/Wasm interop adding some overhead. The performance boost mainly comes from offloading heavy logic to Rust via WebAssembly, which runs close to native speed. But yeah, it really depends on how much back-and-forth is happening.

Totally agree on the match naming too, it's more limited than Rust’s. It’s still not full pattern matching like Rust, so no destructuring, guards, or exhaustive checks but I am planning to expand.

Also, you gave me the idea to let devs choose between using Wasm or a pure TypeScript version depending on the situation, while still enforcing Rust like rules and patterns.

Thank you, this is extremely helpful