| I think that people should understand what this represents, because I think most HN readers (let alone everyone else) won't get it. 1. Start from the Community Edition of VCV Rack (GPL licensed) 2. Redesign the fundamental architecture to match the way most other audio applications work with respect to interacting with audio hardware 3. Implement new modules to replace the most critical ones provided by the non-gratis VCV Rack Pro (plugin version), including sync with the host, exchange audio & MIDI with the host and more. 4. Create new GUIs for the Fundamental module collection that comes with VCV Rack, since those designs are not freely licensed, even though the modules are. 5. Identify VCV Rack modules licensed under "GPLv3 or later", and add them all to the build system, frequently requiring licensing clarification from module authors since the Rack world has been, uhm, a bit, uh, loosey-goosey with this. 6. Find or implement ports of the dependency stack for Rack to WASM 7. Port Rack itself to WASM, which requires a completely new audio/MIDI backend to deal with webaudio and webmidi. 8. Identify and fix browser-specific issues It is a remarkable effort, and Filipe receives essentially nothing for what he has done. |
It's indeed amazing. Do you know him personally? What does he do to earn a living? Does he do consulting on the side...?
In my (limited) experience he responds to issues almost immediately, and seems to be full-time on this; incredible.