nih-plug VS areweguiyet

Super cool. Any experience doing audio/synthesis/DSP work with this in a Flutter app? It would be particularly awesome if this enabled building VST plugins with Flutter and one of the Rust crates for VSTs (like NIH-plug or similar).

Looks nice! Rust really is a perfect fit for real-time audio software. At work we also use cpal for audio output, and has found some bugs as well. In my free time I'm tinkering with CLAP plugins for Bitwig, your app looks quite similar to Bitwig Grid which I like a lot. Maybe providing it as a plugin would be a future option.

I don't think Max4Live is not a good choice for building audio plugins. It's a weird platform that was designed for 'institutionalized academic music,' as I once read someone describe it. It's difficult to program in and not efficient. None of my favorite music software is made with it. It's also quite buggy, in my experience. For doing some basic extensions to Ableton Live specifically, beyond what VST allows access to, it's OK, since it's the only official way to do so.

If you want to just dive into DSP using wires and boxes, with some additional code sprinkled in, SynthEdit or Reaktor Core are faster, more fun, and produce better results. If you don't mind C++, check out iPlug from REAPER's WDL codebase: https://www.cockos.com/wdl/ — there are some forks of it.

There's also JUCE. You'll find some people complain about it and some people regret using it, despite it being relatively popular.

There are some Rust things for doing VST (and AU) development. Here's one that I've seen a few things made with: https://github.com/robbert-vdh/nih-plug/tree/master I wouldn't worry too much about the differences between C++ and Rust in this world. Audio software tends to be buggy, so the bar for being considered 'good enough' is pretty low.

There’s nih-plug for VST and CLAP plugins

As it's written in Rust, perhaps it could be implemented as a CLAP plugin. This is a nice framework I've been playing with https://github.com/robbert-vdh/nih-plug/

The potential is both in terms of moving away from proprietary corporate-controlled standards (but also still providing shared wrappers to support those "legacy" :) audio plugin formats) and supporting Rust as a first class development language (via e.g. https://github.com/robbert-vdh/nih-plug).

Yep, Steinberg licensing sucks. I suggest you use nih-plug, it has a much nicer Rust API and supports generating both VST3 and CLAP plugins from your code. I'm only targetting CLAP nowadays, but unfortunately not many DAW's support it.

Your best bet is probably nih-plug.

The organization behind QT (QT Group) has pretty onerous licensing terms.

My understanding is that it's $3,950 per year just to develop using their libraries on your own computer if you ever in the future intend to commercialize a product using QT. Transitioning from the open source license to the commercial license is something you can do but it's not the happy path and their FAQ seems to indicate that it comes with some sort of penalty.

https://www.qt.io/pricing

Something like Slint (Rust based but includes CPP and JS bindings) is not as comprehensive (yet) but it's more modern and the licensing terms are significantly more in line with software industry norms.

GPUI from Zed is also something to monitor: https://www.gpui.rs/

Also, in general you can find an extensive list of Rust-based native UI libraries here: https://areweguiyet.com/

I would suggest that nearly every person on this website is a developer. Both C and C++ let you shoot yourself in the foot quite easily, but at least C++ has RAII.

If you're referring to Rust, it's just not there yet for anything serious: https://areweguiyet.com/

I normally use python to do some quick data analysis, with pandas/polars/pyspark/...

But I've started to use rust more and more in the last few weeks and really start to like it.

Does anyone have experience doing data analysis with rust, and would you recommend it over python?

And are there any resources like https://areweguiyet.com/ but for data analysis?

You still haven't said anything about why those existing frameworks don't count. Again, they are used in production and do exactly what a gui framework is supposed to do. Sure they may not have all the features of the frameworks that have existed a decade before rust even existed but the issue is time not rust itself. They very clearly can be used to build complex UI without inheritance. Since you mentioned it, you should probably actually look at it https://areweguiyet.com/ the page clearly says that GUI frameworks do exist in rust.

The web site https://areweguiyet.com/ has a list of GUI libraries for Rust.

I haven’t tried any yet as I lack the time, but it can be a good starting point.

Iced and Slint where interesting when I looked at that, and Slint may be done by former Qt developers.

I also hope that it is consistent with the goals mentioned at https://areweguiyet.com/