On Sunday 18 December 2005 19:33, Martin Peach wrote:

> Csound5 is starting to look like a real hodge-podge of stuff. The stk 
> page says this: "all source included, no unusual libraries, and no 
> hidden drivers" about itself. In fact it looks as though one could do a 
> whole lot of synthesis using stk alone. What is csound for? It seems 
> like just that: a collection of unusual libraries from various places, 
> the whole structure made inconsistent and unstable by a single change in 
> any of them. Earlier versions of csound seemed to be more or less 
> self-contained but now so much of the functionality has been offloaded 
> onto code from other projects that perhaps it would be better to develop 
> a csound operating system instead of a program.
> I would have enjoyed having a csound core library with no graphics, 
> MIDI, OSC, python, tcl/tk, etc., one that could be used for sound 
> synthesis. I thought the api would provide this but I can't compile it 
> because it needs all this other stuff, which I don't need. In fact it 
> seems like I could make most of csound out of stk or pure data. This is 
> a bit circular, no?

Well, it is not me who is pushing for the inclusion for all the "extras"
like STK, Tcl, etc. but it should be noted that most of the above is
optinal, and you can easily build Csound 5 with only the API library,
command line frontend, and basic opcodes of which most was already present
in Csound 4.