Cleaning up the docs won’t require another major version, but we want to get it done before we get there.
The expansiveness of the core library is a great virtue… with the side effect of making itself a particular challenge to navigate, in certain cases.
Before stepping aside for a moment, a more in-depth report of SC’s user survey:
Top result: tutorials & documentation
Top result: tutorials & documentation
The preceding question appears to be a summary of category groupings for responses to a free form version of the all the questions that comprised the greater majority of the entire survey… user interest regarding areas of potential future development.
The result ratings for these questions can be shown in their entirety by using only a single image or inforgraphic, serving as the grand takeaway concentrated gem of information, from over 11,000 questions & answers.
Here are the results for score ranked features answered by every user in the survey:
…while being dead last on the list, the support for Ableton Link (see LinkClock) is still a victory none the less.
While nearly all of the features could be reliably implemented without a major version update, the outstanding exceptions seems to be support for VST plugins as well as standalone applications.
If both of these implementations were included as cleanly polished & functional interfaces… this in itself would be mark a huge distinction from SC as it is at present.
Not to draw relevance from the evolution of how the community currently feels about this; I find these two features to be the highest demand overall, and while apart from being distinctive in nature, VST &
Standalone have captivated my interest rather naturally, since I first began using SC.
Standalones were once possible on OS X, and as @jamshark70 mentioned, the critical issue with these involves licensing… and a similar issue exists for VST that also involves licensing related complications.
The necessity of popular demand may work as a catalyst for the next prefixed version release of SC… this in itself would require the licensing updates to reflect only the identifying and applicable versions of future releases.