If you want to be the only person contributing to the official JUCE repository then you will have to draw a line at what you will, or will not, work on. Since your output is by definition finite. As a single programmer, I would think that you have to be absolutely ruthless about not reinventing the wheel. Because each hour that you spend replicating existing functionality, is one less hour for new innovating things (like secret sauce).
What did we gain from a code editor in the IntroJucer? No offense, but it can’t compare to existing editors. Not even close. I’m thinking SublimeText and Visual Studio. Those products are dedicated to one thing, and one thing only. So they will always be better. Since there’s no font hinting on Windows (yeah I know its a sore subject) all the text looks horrible. I built the JUCE demo and IntroJucer on Linux and WOW the text looks so much better! And where’s the parameter completion, symbol browser, etc… in IntroJucer? I’m at a loss to figure out what the target audience for editing code within the IntroJucer.
I also have my doubts about this. Without question, JUCE development has been considerably slowed in the last few months. Many items have been marked as “don’t have the time for.” I’m usually a very conservative programmer. I don’t like it when the tools change, and I have to be really sold on something before I accept a change in my workflow. This “secret stuff” seems like it is all tools. Which I will probably not use. I would much rather see energy directed towards fixing bugs and making improvements to the actual library code which ends up on in the final executable.
This all reminds me of the Inner Platform Effect.
On the other hand I certainly understand that after years of development on the same thing it is a welcome change to have something new and exciting.
Since I use git-subtree to bring in the JUCE repository I hope that we dont see the official JUCE repo swell up with a full copy of the LLVM source tree - it would be best in a separate repository. In fact, I wish that the JUCE source tree was its own repo, with the extras in a separate repo but I guess its too late for that now.