Wow, been using DAWs since 1992 (and straight up sequencers synced to analogue reels or decks since the mid 80s). Never had a problem with this. Nothing wrong with pointing out an idea for improvement to the UI, but I wouldn’t throw up ‘other DAWs’ work flow as rationale for implementing it. In time, you’ll learn that Cubase has quite a few things that no other DAW on the market even tries to touch yet (and probably never will). In time, you’ll also discover that very few DAWs on the market offer as many work-flow options (methods, editors, track types/styles).
On bringing the Remote Device portion into the ‘century’, they could do it, and that would be a SAD DAY, because then 50+ years worth of legacy support just might go out the window. The ability to build your own (if sysex, RPN/NRPN events, etc. are required) pretty much goes away, or turns into a nightmare of ‘hoping’ instrument developers include files or profiles/drivers with the device, and when they don’t, the voodoo required to ‘make your own’ is rarely documented.
Quite a few studios keep Cubase around for the simple reason that newer DAWs on the scene cannot cope with mounds of very fine equipment that have been released over the decades, at all. Also, a lot of newer DAWs try to duplicate things we’ve simply done with better suited plugins, outboard gear, or the instruments themselves for…well…decades now. It’s also kind of nice that we can still get Cubase up and running on rather old hardware, with a fraction of the cores and memory that newer DAWs often require. In Cubase, you can still remote control ultra fine parameters of an actual Yamaha DX7 from nine-teen-eighty-weird right there in the track inspector…try that with other DAWs…
On putting out demands for ‘new features’ over reading manuals and being flexible with work-flow… I see people screaming all the time about wanting to oscillate a band of frequencies with an LFO on an EQ plugin with a VST controller lane. Suggest just using a notch-filter plugin that has LFO built in instead, and they look at you funny. Suggest implementing the ‘effect’ through the VSTi’s built slate of effects instead, and they pound their chest, “Umm no! The DAW should pump this control…not the plugin itself!” Suggest investing in something like Bidule, that has very flexible comb filtering abilities, and so much more…and, “Oh no! I shouldn’t have to use anything third party…EVER!” Suggest just using a MIDI LFO insert to generate a static curve, then copy and paste that into the VST automation lane (thus saving some CPU cycles), and oh lord…no, no, no. Old workflows must GO.
I’m all for adding some of these things to Cubase, but we have deeper issues…little bugs, and power user utilities that in my humble opinion should take priority. Different teams work on different aspects of the total package, but in the end, dev time and assignments have to be spread out. If we already have plugins and stuff that can do it, just as well, or even BETTER with a different thought process, or an adapted work flow…it’s worth considering.