I agree. High-end audio manipulation will remain native, but I think for a simplified use-case (composition, lower quality renders) the browser is a good sell.
That and the tooling is almost here with MIDI.js[1], Web Audio[2] and Web MIDI[3] as a working draft.
In fact, latency and audio quality (because of file sizes for sampling and because of available resources for synthesis) are two big limitations in a browser.
Also, we want to enjoy the capabilities of the MIDI output features, in order to route MIDI signals to Virtual Instruments on the computer (through virtual MIDI ports)
In fact, latency and audio quality (because of file sizes for sampling and because of available resources for synthesis) are two big limitations in a browser.
We have big expectations about the upcoming Audio Workers ( https://github.com/WebAudio/web-audio-api/issues/113 ) to release advanced synthesizer.
Also, we want to enjoy the capabilities of the MIDI output features, in order to route MIDI signals to Virtual Instruments on the computer (through virtual MIDI ports)