I thinking about playing a bit with audio and the JUCE C++ framework for creating GUIs and DSP apps/plugins. JUCE comes with Projucer which scaffolds a project for Xcode or Visual Studio.
If Nim can compile to C++ is it correct to assume I could write Nim code which then produce C++ files which in turn would be compiles by Xcode?
Someone is yet to write a JUCE library for Nim.
Out of curiosity, what made you choose JUCE over the alternatives?
JUCE has a big down-side of being GPLv3/commercial licensed, and thus not very popular. The two most popular portable GUI choices, Qt and GTK both use L-GPL. But I think Nim can do even better by focusing on something new and genuinely free...
Related:
JUCE is not a GUI library. It is a specialized toolkit for audio/video/DSP/plugins/MIDI software creation which also includes some GUI support.
OK, I guess this means that Qt-related audio libraries (ex. SigDigger, QMidi, etc) aren't as good?
There's nothing bad in dual licensing. Qt still has dual license (https://www.qt.io/licensing/).
I guess you didn't read what I said closely. Which license is involved (GPL or L-GPL) matters a great deal. This was of particular concern for KDE, and there was an agreement in place for Qt to be released as BSD if abandoned.
I mentioned licenses only in describing how JUCE compares for most people. People are less likely to invest time adding Nim support to a large framework they can't use in all circumstances due to legal restrictions.