sharke
It does sound like Reaper has a much better design philosophy when it comes to handling plugin crashes etc...from what I've heard a plugin crash or incompatibility will not cause Reaper to hang, instead Reaper identifies the problem and resets the plug while remaining stable itself. Not sure how accurate that is, just going by comments I've read from others.
The VST thing I can confirm. I forget which VST I was using, but it crashed, Reaper put a message on the track that said it was not responding (or something to that effect), it reset the VST, and kept working. I didn't even have to close Reaper, it just kept chugging along like nothing happened after about 15 seconds.
I know it was the VST that crashed for two reasons, 1: Reaper told me it was this particular VST by name, and 2: It crashes all the time in Sonar. I always freeze immediately when I use it. I don't know for sure if it responds this way to all VST's when there is a problem, but I can confirm it did in this case. Another thing you can do is, there is a setting you can check off in Reaper to help make unstable VST's work better. I haven't tried it because, well ... it's never crashed or given me any problems.
If that is the case then Cakewalk should definitely look toward following that path, because I'm sure a lot of these crashes are to do with instability in 3rd party plugs taking Sonar down with them.
The VST I was using was one that comes with Sonar ... but I can't remember if it was one they did themselves or if it was one of the 3rd party ones they use.
Reaper supports VST3 ... maybe that has something to do with the fact that it was able to reset it like that? I was mistaken, it does not support VST3.