That is true. My impression of Cubase is based on issues I have experienced myself, things I did not experience, but I am shocked to see they made it into a release after reading the fixes in the patch notes and reading here what people report. That means, some of these issues are not directly affecting me. But: it all leaves a very sour taste using the product, never knowing when you run into the next thing that annoys you, disrupts your work or even might cause lost progress on a project. I do not feel confident in Cubase at all since version 10. And seeing unfixed issues every day that exist for years now does not improve that confidence.
And I do make an important distinction. I have no problem that there are bugs which might be very exotic, only in very rare constellations under certain circumstances. Stuff that only comes to light when you have a very broad testing bed “in the wild”. Thats fine and normal! But issues make it into major releases every year that are just new features not working as intended, because they were not tested enough and not ready. And some of the issues that make it into releases are visible within minutes of actually using the DAW. For example the completely broken UI of Retrologue and Groove Agent SE 5 in the C11 release on Mac. They were a clearly visible mess, and it was released anyway. Or the CPU overload indicator that is annoying people since 2017, a known issue, visible every day, never bothered to be fixed. I just found a clearly visible bug with the virtual keyboard that you’d discover just by browsing presets. Saw that within 20 minutes of dabbling with the latest update. I wonder how no tester could see this or if it is another “known issue not yet scheduled for an update” by Steinberg.