It’s clear that the main point of JUCE is to simplify cross-platform development. But let’s say I wanted to develop a MacOS-only audio app; is there still a big advantage to developing with JUCE?
While MacOS’ CoreAudio Framework is nothing to shake a stick at, you’d still benefit from the wealth of audio-related knowledge in the JUCE codebase - and there is a lot of code in JUCE that you may end up re-writing for your MacOS situation, too - such as the DSP and related classes.
1 Like
Hello
You never know what the future will be. If you develop with JUCE, you will have the opportunity to switch to another OS at no cost. If your code is platform dependant, well …
Besides JUCE is really a nice framework really well-done.
1 Like
Until two weeks ago I would have recommended JUCE as a no-brainer.
Today I have to say, have a look what you need as dependency.
4 Likes
I assume you’re referring to the new license terms? I would fall into the “Indie” category, which means a perpetual license of $1000. This doesn’t seem too unreasonable. Also it appears that the Juce management team is considering adjustments to the licensing based on a lot of negative feedback.