i think this is a bit of dilemma.

there *are* users for whom this kind of separation is potentially or actually very important. hiding such functionality is a lot easier than adding it later, but is not always totally successful. if one is writing software that might be used in  situations outside the home/bedroom studio, the considerations for what should and should not be exposed directly to users get a lot more complex.

i am thinking here of robin's upcoming video timeline work for ardour3, which also features an external server to handle generating keyframes. when i asked about this he pointed out that in many professional workflows where the video consists of uncompressed raw video, you don't have enough CPU power to do both that and run ardour and/or there may be restrictions (from people who make "the rules") on how easily you can move the data on a random machine used for audio work. now of course, for the overwhelming majority of users this feature is completely redundant (and hopefully for those users, ardour starting said server in the background on their own system will hide most of the ugliness). but i do think that those of us who actually or hopefully interact with these sorts of professional scenarios have quite a difficult task with this sort of thing, and its one where apple have not (thus far) prepared a roadmap of "how to do it so that users really don't get inconvenienced".