When comparing DAWs, most of excitements or disappointments are about HOW you can use it. GUI (in some DAWs almost completely customizable, no point to compare just one theme), shortcuts, how you achieve something, which "wonderful" screens it has. FXes/Synth included.
Compatibility is for sure is important point for particular use cases. And at least I see some comparison in the area.
I mean 32bit, DX, MIDI VST, hardware.
Stability and performance
But what is hard to find is WHAT you can produce. I mean which features of the information inside your project file are the same / different / exist / omitted. Making such comparison during Sonar->Reaper conversion, where I had to found how Sonar project feature A can be mapped to the Reaper project feature B, I have discovered:
1) unlike almost infinite list of "how" you can do things, the list of "resulting features" is rather short
2) the difference in what is saved as "your work" is even shorter
3) the list of "DAW B can not save the following results you can produced in DAW A" can be posted in several lines.
So, the following "project features" of Sonar can NOT be transposed to Reaper:
a) no grove pitch markers and so loops can not follow them
b) not found yet
I have nothing explicit to put into the reverse list (Reaper -> Sonar). There is one "too buggy" area in Sonar to use in practice: intensive in project MIDI routing, but it "exists".
Note that I have not converted/compared Stretch Markers (Reaper) with AudioSnap (Sonar). Almost everything else is converted or at least analyzed.
Since after closing the DAW the project is the only thing which persist, I think when something is not there, that can be the major "show stopper" when using the DAW. So, how such list looks for Studio One?