News for hackers. Stuff that matters.
Re:Audacity 4.0 by Joel_Mckay on Thursday September 03, 2026 @09:58AM (#49550005)
wxWidgets uses the native OS interfaces. They have a valid point about Qt sometimes breaking things, and should be packaged as an audacity-qt6 fork.

Your perspective is also valid, in that it could be phrased a little kinder. =3

Re:Audacity 4.0 by epcoa on Thursday September 03, 2026 @10:51AM (#49550704)
> wxWidgets uses the native OS interfaces.

Audacity was fooling no one that it was a native MacOS app, or even a particularly well designed GTK app. The fundamental idea of WX is not sound. Turns out MFC is not a great abstraction for AppKit.

Even Qt uses some higher level native UI interfaces on its respective implementations.

Re:Audacity 4.0 by torstenvl on Thursday September 03, 2026 @07:20PM (#49558487)
In what way is the fundamental idea of wxWidgets not sound? It works very well, and is pretty much the only toolkit to do what it does.
Re:Audacity 4.0 by epcoa on Thursday September 10, 2026 @07:25PM (#49651503)
Trying to shoe horn multiplatform UI into MFC? Just look at Unicode. It’s an unholy mess.

The only toolkit to do what it does? Qt does what it does, even if the approach is not the same (arguably superior), there’s also Tk. There’s also libui and IUP.

Re:Audacity 4.0 by torstenvl on Tuesday September 22, 2026 @10:40AM (#49802120)
> shoe horn multiplatform UI into MFC

This is nonsensical. What are you even trying to say here? MFC isn't available on macOS or GTK.

> Just look at Unicode. It’s an unholy mess.

This seems utterly unrelated to the issue under discussion.

> Qt does what it does, even if the approach is not the same (arguably superior), there’s also Tk. There’s also libui and IUP.

None of those allow a single codebase to compile on Windows, Mac, and Linux, and get native UI elements on each.