Downsizing the Class Library

[mike]

Two major concerns have been raised:

1. breaking backwards compatibility
2. trimming the core so much that the default install is lackluster/less powerful from a new user’s perspective

@scztt speaks to those the points elsewhere:

@scztt

Note that moving core functionality to a quark does NOT mean removing it from the default install (e.g. the “minimal PD” edition that is equally loved and loathed) - it would be straightforward to have a default list of quarks already-installed as part of the base SuperCollider app package. It would simply mean that parts of what is now the core class library could be versioned separately from the core library, and in a predictable way - this would mean e.g. @julian could make major upgrades / breaking changes to JITLib without requiring that users with “old” jitlib code be stuck on an old version of SuperCollider forever - obviously a big benefit.