> Let us look at Windows and macOS for a second here, and exclude Linux, because Linux (rather, Linux + your favorite DE) is realistically the issue [...] If you design around a given language for the most recent versions of a native OS, you'll never have issues. Both macOS and Windows include common libraries that map to their respective styles.
That is a bold statement and largely not true.
Most DAWs are only developed and maintained for Windows and Mac. Almost all of them are using their own set of widgets/gfx because they want control on their style and they want it to be the very same on both Windows and Mac. Their software is very specific and want their tool to look and feel like hardware, not a regular software.
It is mostly about control. Linux doesn't have anything to do with that and any software maker can decide to only support GTK or QT, libwine or whatever toolkit it wants to use and stick with it. Linux users are used to run QT apps on Gnome or GTK apps on KDE, they are not the one that would complain and given the market share, the software companies are happy to give the middle fingers if they do so anyway.
That is a bold statement and largely not true.
Most DAWs are only developed and maintained for Windows and Mac. Almost all of them are using their own set of widgets/gfx because they want control on their style and they want it to be the very same on both Windows and Mac. Their software is very specific and want their tool to look and feel like hardware, not a regular software.
It is mostly about control. Linux doesn't have anything to do with that and any software maker can decide to only support GTK or QT, libwine or whatever toolkit it wants to use and stick with it. Linux users are used to run QT apps on Gnome or GTK apps on KDE, they are not the one that would complain and given the market share, the software companies are happy to give the middle fingers if they do so anyway.