There's entire ecosystems of plugins out there. Yes they can be reimplemented but if the authors use the same quick algorithms as everyone else it's going to sound plastic-y and dull. IMO plugin dev is one of those things where every hour spent makes a cumulative difference in output quality.
WASM may be great, but unless they can run as their own binary in their own windows you're going to have browser overhead for each window, nevermind those of us that spread our DAWs out across multiple screens.
I use Audacity like a DAW. Please clarify:
"Audacity is a free and open-source digital audio editor" [0]
"A digital audio workstation (DAW) is an electronic device or application software used for recording, editing and producing audio files." [1]
You can use Audacity to record, edit and produce audio files.
* no real time effects playback
* it doesn’t support VSTi’s (long standard and expected)
* no sequences
* can’t use MIDI controllers
It’s a fantastic platform for recording audio and post-processing, it is a terrible music production program, which even the most basic DAW’s can handle.
To make a video comparison, it’d an like an NLE that can’t sync audio/multi cam, has an unintuitive and semi-bloated UI, doesn’t support captions, and can’t support multiple timelines under one project.
Shoddy support for platforms other than Windows, not to mention VSTs going out of support by the developers and then unusable when something changes (e.g. Apple dropping support for 32-bit x86 years ago).
WASM is at least a common denominator supported everywhere... basically Java just better.