2 ms·
I guess I have to disagree Paul, even though of course you're the one with practical experience in this specific niche since I didn't write a DAW from scratch.
by tialaramex 5y ago
I guess I have to disagree Paul, even though of course you're the one with practical experience in this specific niche since I didn't write a DAW from scratch.
Since you compared it to a web browser maybe it's instructive to remember that a big reason Rust had initial traction was that Mozilla had tried, and failed more than once to make key improvements to some of the browser's thorniest concurrent code in C++ but using Rust made this practical at last.
C++ is horrible and I think you're under-estimating just how much difference that makes in this scenario for something like Ardour.
- PaulDavisThe1st 5y agoThe thing is, something like Ardour doesn't need "key improvements to some of [our] thorniest concurrent code in C++". We're in good shape there (perhaps because the requirement that most of our concurrent code has to fit in with RT requirements pushed us to do better design work there). We need to people more than anything to do workflow stuff (mostly GUI). Some years ago, I did several talks where I touted the idea that us adding a web interface to Ardour, so the generation raised on the idea that programming means HTML+CSS+JS could go to town and do new cool things (or at least, create new "cool" UIs). We've failed/chosen not to publicize the fact that we have a web interface now, but my position on this has changed. I was wrong about the web interface. I just don't think we're going to get significant numbers of new contributors no matter what language or development environment they could use. We have on the order of 100 contributors already, and I think that if we ever got to 200, it would be a miracle. Even 25 new contributors would be a change in our developer resources that would be game-changing.