> If you write any application in "native" widgets for the host OS, shame on you. That is definitely the wrong way to do things in almost every case nowadays
Could you elaborate on that? Isn't using the native GUI API of the OS a relatively sensible default, especially if you aren't targeting multiple OSes? If you definitely want cross-platform support, I can see the argument for choosing one of the cross-platform frameworks but I still don't think that means using the native GUI API is such a bad choice.
Qt is a great choice for writing multi-platform desktop apps. It would take a lot longer, and add unnecessary complexity, to write the UI specifically for each platform.
I suppose for OS utilities targeting a specific platform only, that makes sense. But for portability, you sure as shit shouldn't be trying to write a custom GUI using the native OS GUI toolkit for all three platforms. It's surprising how many make this mistake. It's like they've never heard of Qt and are surprised development takes forever.
Could you elaborate on that? Isn't using the native GUI API of the OS a relatively sensible default, especially if you aren't targeting multiple OSes? If you definitely want cross-platform support, I can see the argument for choosing one of the cross-platform frameworks but I still don't think that means using the native GUI API is such a bad choice.