4 ms·

hard disagree here. Let us look at Windows and macOS for a second here, and exclude Linux, because Linux (rather, Linux + your favorite DE) is realistically the

hard disagree here. 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 (due to KDE, GNOME, and a gazillion other types/styles). 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. Microsoft, for example: https://docs.microsoft.com/en-us/windows/apps/design/ https://docs.microsoft.com/en-us/windows/apps/design/ (link on bottom if you want to drill down to code). "What about users that want to customize things?" Give them an alternate path. The browser loads slightly slower (the same as now), and they still get their ability to customize. The rest of us can use the default, faster path.

prmoustache 5y ago
> 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.

prmoustache 5y ago

> 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.