Kenny beat me to it.
 

bapu
 
Or, how about "it's a console, with some limited MIDI fluff you may or may not use"?

I suspect that's how most users view it.  Of course, I may be wrong.  But I do think it's a bit unrealistic to expect Mixbus to rival Sonar in MIDI/VST handling when the latter's VST hosting has evolved over what, 20 years? (I'm not including the pre-VST decade before that).
 
I'm all for consolidating and streamlining wherever possible; I just don't see the benefit of forcing MB to be a MIDI workstation when that's just not where it excels. For example, I currently use Sonar (MIDI production), Mixbus 32C (Audio mixing. Just recently, still in testing mode), then finally Studio One 3 Pro (for its excellent Project-Mastering page).
 
Again, using the best (IMO) tools for each job.  Now, while I don't see myself ever dumping Sonar for Mixbus' MIDI capabilities, I could easily imagine retiring S1 3 Pro if MB were to ever add a solid Project-Mastering feature-set.

JonD

bapu
 
Or, how about "it's a console, with some limited MIDI fluff you may or may not use"?

I suspect that's how most users view it.  Of For example, I currently use Sonar (MIDI production), Mixbus 32C (Audio mixing. Just recently, still in testing mode), then finally Studio One 3 Pro (for its excellent Project-Mastering page).
 
Again, using the best (IMO) tools for each job.  Now, while I don't see myself ever dumping Sonar for Mixbus' MIDI capabilities, I could easily imagine retiring S1 3 Pro if MB were to ever add a solid Project-Mastering feature-set.

 
 
Jon, I think that is how I might revise my view and workflow. With the exception of owning Studio 3 for mastering (Ozone or Neutron may bear experimenting for me.
 
This will involve learning more about creating  Stems and export from Sonar  and import into MB, but its fun and informative and a great learning experience.