From another thread:
I’m the first to admit that I would rather see 64-bit sample support instead of WYSIWYG code compilation and preview in ProJucer. It would have been nice if Jules had finished providing support for 3rd party modules in the Introjucer instead of leaving it unfinished and jumping to the next new and shiny code toy. But insults are entirely non productive. The best way to be vocal is to be polite but persistent in gently reminding Jules and the rest of the JUCE userbase that there is important work to be done which will directly benefit end-users of software that is written using JUCE (as distinguished from the JUCE customer base, which consists of the programmers).
I’d also like to see better support for native operating system features. Windows 8 has already been released and JUCE is completely unprepared to build applications in the style of this new operation system. Heck, JUCE isn’t even well suited to create native controls on iOS. But badgering Jules about it will likely not produce results.
If you frequent the forums, you will find that one successful approach at getting new features or bug fixes into JUCE, is to simply write it yourself and then work with Jules to integrate it into the library. A recent example is the wonderful outside work that has been done in making the GNU/Linux support more robust.
JUCE has been around now for almost 13 years. Looking over the history of it’s development, it truly is an astoundingly good library. Considering that it was written by one person, I’d say that there is plenty of evidence that Jules has been responsive to customers. The library is unique in that not only does it allow one to build cross platform user interfaces, but it specializes in creating both concurrent audio applications and audio plugins. There is nothing else like it. It is very fairly licensed and priced.
My personal opinion is that perhaps Jules has gotten burned out fixing bugs and adding user requested features and just needed a sabbatical. Especially after the “Jucequake”, our informal name for the massive code reorganization brought about in version 2.0. The Jucequake was a huge success, it ushered in a whole new way of organizing the JUCE source code and also serves as a model for organizing your own source code. This “unity build” style of source code organization was so handy, I had no choice but to adopt it for all my current and future code. Which is quite a rare event because I am quite conservative when it comes to changing my style. Version 2.0 also brought with it the Introjucer which despite being somewhat rough around the edges, simplifies project management across multiple platforms. This is hardly the sign of someone who is unresponsive to customers.
Thankfully, Introjucer is not required for practical development (yet). :lol: :lol: :lol:
Unfortunately we seem to be kind of dead in the water when it comes to significant improvements to the JUCE library. Introjucer never really got finished, and for the last 6 months the answer to most features / major fixes has been that there is “no time for that right now.” Are most of the available time slots for development consumed by Projucer? Maybe. But after 13 years I think a vacation is earned.
I am very interested in specifically seeing more features added to the library and not the satellite system of tools surrounding it. 64-bit samples would be great, more native controls would be great (especially menus). A TextEditor with centered justification. All of the features that have been requested this year that got put off. Hopefully all we need to do is wait for this slowdown of JUCE development to run its course and then we can have the old Jules back.
But if the old Jules is not going to come back for a long time, or ever, it would be nice to have a serious discussion about how we can move forward. It makes no sense to have the forward progress of the JUCE library held hostage to the timetable of a single programmer. If JUCE is going to continue evolving at a brisk pace, I think the current one-programmer model would probably be a bottleneck. We are seeing the evidence of that right now.
It is also unfortunate that a lot of the JUCE folks who I interact with on a daily basis don’t have the fortitude to step up and voice these opinions for fear of upsetting Jules (you know who you are). The chorus of praise in the Projucer thread and the lack of meaningful dialogue regarding delayed features is troubling. If customers cannot have an honest and polite (and I emphasis POLITE!!!) dialogue about their needs and wants, then how can we expect JUCE to evolve to maximally satisfy everyone? Well, at the risk of sticking my neck out, I’m stepping up and saying what needs to be said. I hope everyone can respect that.