Goodbye then, Mr Chips.
If you were to pause from wallowing in self pity long enough to pay a decent amount of attention to the countless threads that are in this forum where people have audio crackles and dropouts, you would have seen that in 100% of the cases the issue was with one or more of the following:
1. Slow computer
2. Little computer memory
3. Cheesy sound card - sometimes even the on-board sound chips
4. Not using ASIO
5. Improper settings for ASIO, such as sample rate mismatch or using too high a sample rate
6. Hardware/software issues with the computer that interfered with audio streaming
7. Anything else along these lines that I missed
My point is this. In virtually EVERY single posted thread on audio dropouts and crackles, it has NEVER been an issue caused by Sonar.
So, you want to go - guess what, your dropouts and crackles will follow you to whatever recording software you think is going to be the Holy Grail. And don't blame Cakewalk for your being too lazy to research that issue, and too lazy to apply that research to properly configure your audio hardware/software environment for audio processing. To the best of my recollection, the rest of us have figured out how to configure things so that dropouts and crackles are eliminated for probably close to 100% of projects out there - although some have to freeze/bounce/etc mostly due to not enough memory in their computers for projects that have a zillion tracks and a boatload of virtual synthesizers. Even those projects have a proven method of getting rid of any audio problems, through freezing/bouncing. That leaves just you, because you didn't take the time or effort to set things up properly.
Are there bugs? Sure, there are. There always will be. That is true of every piece of commercial software that has ever been developed. Maintenance is scheduled and performed on a triage basis, where any show stoppers are dealt with first, and then other fixes are addressed through a variety of methods of determination of things like impact of any given issue to the users - issues that affect more users more often are given more priority than more obscure bugs. That's how things work in software development.
Nonetheless, there are a whole bunch of folks being quite productive using X2, and X1, and 8.5.3 - working within whatever limitations there are, but working nonetheless.
Coffee tastes better when you aren't crying in the cup. Good luck.
Bob Bone