How much is too much!!!!

With software there is no limit to "stuff." It just gets more complicated.  Take MS word.  I use it to make money, but I've never even used 1/10 of its capabilities since I don't prepare to publish with it.  Same with SONAR.  There is plenty of stuff I don't even know exists, tools to do things I never knew I needed, and ways to do jobs I don't do.  But they are all nice to have even tho I don't use them.
 
The biggest problem with the monthly updates (and a nice thing also!) is keeping up with every aspect of a complex DAW and consequently growing your own work load to take advantage of them.   Most people here are not professional users, so a lot of the capabilities aren't needed. But it is nice to have them when you do need them.  It is like owning a van or a truck - most of the time it is too much car, but when you need to move something bulky (or dirty), nothing else works.

yea this isn't like some old play station game were you could only fit 4 GB max on the game disk.
With "Add on" possibility's, it's an infinite thing. Sure there are always tweaks that are going to be needed but I believe the monthly thing has ironed a lot of that out.
 

A hover craft would not be too much.
 
A Cakewalk coffee mug seems to be too much (to offer) though.

The user interface stuff that just lays there waiting for you to click it in an event driven OS like windows consume little to no cpu cycles until you go click on them then they start executing their code. So don't worry about glossy ui stuff too much like the pretty PRV selector for instance. Memory consumption could raise it's head here though.
 
What's maybe more concerning is that while there are at least one pet issue for every user, Cakewalk is choosing to instead of hacking away at them, they are fixing issues that don't really exist yet. For example: We had a PRV track picker and we knew how to use it (and it showed all tracks too, for decades) But now we have a pretty picker with a learning curve. And we're now whining that it shows all the tracks! Now, I know it's hard to keep coders happy just bug fixing and they'll got somewhere else as it's much more gratifying to create. But the installed base by and large doesn't see it that way. There are things that worked in X1,2 & 3 for instance that don't in the New Sonar. Like I said, at least one issue for each user.
 
Now that many have lifetime updates it also takes away any leverage we may have had.
 
Suck it up, ButterCup!
 
Addendum: I can read and write C / C++ and would welcome the opportunity to fix some of my pet issues.
I'd do that for free. I have lifetime updates and a vested interest in at least one big ACT issue. I'd love to tackle that.

I see two issues at play. The first is adding more "stuff" that is for specific users, and which don't matter to others. For example suppose SONAR did a serious revamp of video support. That would involve a lot more "stuff," but it would add nothing for those who don't use SONAR with video.
 
But I also think there may be a tipping point where SONAR starts to consolidate features into an easier workflow. IOW there would be no less functionality, but it would be streamlined and easier to access.

paulo
Apparently it's "not possible" to produce software that doesn't require fixing to some extent, so I guess CW will always have something to do.

In case they ever DO figure out how to produce 100% bug-free software, then there will be a Windows update with a glitch and...