2 ms·

> There's no way I'd dare to take on a full Apple-platform app project alone on my own And that's really sad, because earlier Mac OS X (and even OPENSTEP to a

by steve1977 2mo ago

> There's no way I'd dare to take on a full Apple-platform app project alone on my own And that's really sad, because earlier Mac OS X (and even OPENSTEP to a degree) was an Eldorado for boutique developers, not least due to frameworks like Cocoa and Objective-C (despite all the hate it seems to get). If you knew C, it was not hard to grasp Objective-C (at least it was much easier than say C++ and MFC on the Windows side of things).

Razengan 2mo ago
That's actually why I jumped from Windows to Mac in the first place! My first Apple purchase was an iPad I got for my aunt, and I loved how streamlined yet powerful it was so I installed a VM on Windows to dabble in iOS development, and fell in love with the sheer consistency of macOS, iOS and their APIs. This was during the era when Microsoft was still figuring out whether to keep the Start Menu and replace the whole Windows UX with a tablet UI, so it was an easy jump. Almost never looked back, and whenever I do I'm glad I jumped. Then came Swift and I loved it, but then it took literal years to catch up with everything you could do in Objective-C with the Apple APIs. SwiftUI is having the same problem but for much longer :(
- viktorcode 2mo ago
  > Then came Swift and I loved it, but then it took literal years to catch up with everything you could do in Objective-C with the Apple APIs. I don't get this part. You can literally rewrite Obj-C code verbatim in Swift and it will work. The only missing part is C macros.
  - Razengan 2mo ago
    > You can literally rewrite Obj-C code verbatim in Swift and it will work. It took a while to get there. They didn't have native Swift APIs for some things like URIs etc until later.