| ▲ | littlestymaar 3 hours ago | |||||||
> C++ and Python map extremely well to Qt which is one of the predominant UI frameworks Qt used to be predominent, but it really cannot be said in 2026 given that there's probably two orders of magnitude between the number of React Apps and the number of Qt ones being made in this decade… > Just because new paradigms are made, doesn’t mean the old ones are inherently bad either Yet barely anyone uses the old ones anymore. Surely it must not be only because people like new and shiny things (React being more than a decade old at this point makes it far from “new and shiny” anyway). > ObjC maps really well to AppKit/UIKit. This example is particularly interesting given that Apple moved away from their old UI tech on favor of SwiftUI, which isn't OO-based. | ||||||||
| ▲ | dagmx 3 hours ago | parent [-] | |||||||
1. I said “one of the predominant”, that there are other frameworks ahead of it doesn’t mean it’s not in the top set of UI frameworks. Especially for native apps and automotive / medical use cases. 2. I think you might be living in a bubble if you think “barely anyone uses them”. Qt still has massive use , entire industries are dependent on it. 3. This is a misunderstanding of SwiftUI. Many aspects of the underlying parts of SwiftUI are still AppKit/uikit based. It’s about declarative vs imperative, and about react style development. SwiftUI being better doesn’t mean that the old paradigms were inherently bad or unsuitable like you suggested | ||||||||
| ||||||||