I’m checking out JUCE for my first audio app, a commercial project. It looks sweet! I’ve done lots of MIDI programming, “realtime” and file I/O, but am new to audio. I’ve also done lots of (not always pretty) GUI/app programming with wxWidgets.
JUCE looks really great and I’m impressed by the list of users, but when I see Jules’ comments about no plans for JUCE 3.0, and look at the posts over the last year+ asking about Vista/WaveRT(?) support, Cocoa support, and general 64-bit support, I see Jules’ hesitation to update the code and unless I’m mistaken he’s the only one who maintains the code. This makes me unsure about JUCE’s future as a toolkit, especially for choosing it for a new project.
Jules, could you share your thoughts about the future of JUCE and your involvement? If you were to decide not to actively keep developing it, would there be any problems releasing it as a full open source project with contributions from the community keeping it going? But that would complicate things for commercial use. Are there any other developers who’ve been sharing maintainence with you? I’m not interested in pushing you in any particular direction, just would like to get a feel for JUCE’s longevity.
BTW, since I’m new to audio, if you anyone has some favorite refs for learning audio programming (device and file streaming, realtime processing) please let me know. Thanks!
Also, I’m impressed with the breadth of JUCE’s functionality, especially from a single developer. Jules, did you build this all yourself, or is the ComponentPeer core from Java somehow?