3 ms·

What would I learn there?

• pjmlp 10mo ago
  That development on macOS UI frameworks isn't as rosy.
  • steve1977 10mo ago
    I'm not saying it's perfect. Just that it's less of a mess than the situation on Windows.
    • pjmlp 10mo ago
      Again, listen to those podcasts, especially how Apple has (not) handled bug reports. Between Carbon, Cocoa, UI Touch, UI Kit, Catalyst, Swift UI, there is plenty to chose from, with many non overlapping capabilities. Then there is naturally the whole plethora of Kits, with several deprecated and replaced by others without feature parity, https://marcoeidinger.github.io/appleframeworks/ https://marcoeidinger.github.io/appleframeworks/
      • steve1977 10mo ago
        Carbon is long deprecated and as mentioned was only ever meant as a transitional framework. Cocoa still exists and is usable. UITouch is not a framework, but a class in UIKit. UIkit still exists and is usable. Same for Catalyst. Same for SwiftUI. As said, I'm not pretending everything is sunshine and roses in Apple-Land. But at least Apple seems to mostly dogfood their own frameworks, which unfortunately doesn't seem to be the case anymore with Microsoft. WinUI 3 and WPF are supposed to be the "official" frameworks to use, but it seems Microsoft themselves are not using them consistently and they also don't seem to put a lot of resources behind them.
        • pjmlp 10mo ago
          Win32, MFC, Windows Forms, and WPF also exist and are quite usable. Apple also doesn't always uses their stuff as they are supposed to, Webviews are used in a few "native" apps, some macOS apps are actually iOS ones ported via Catalyst, which is the reason they feel strange, and many other stuff I could list. Two measures, two weights.