3 ms·

Writing a brand new Mac app for myself, using Objective-C instead of Swift. So far it's a breeze. Yes I used Swift for a while, and it sure feels all academic a

Writing a brand new Mac app for myself, using Objective-C instead of Swift. So far it's a breeze. Yes I used Swift for a while, and it sure feels all academic and all, but meh, ObjC gets the job done just fine for me.

pohl 10y ago
Objective C will always have room in my heart, but I'll never go back to it. There's too much .h ceremony.
- sdegutis 10y ago
  Meh, I've spent about 20 hours on this project so far, and I'd estimate probably 2 minutes of that time was spent managing .h files.
  - yoz-y 10y ago
    Do you have any concerns about maintainability? So far Apple has been advancing Obj-C interfaces along with Swift, but time will probably come when some new OS features will only be available through Swift.
    - sdegutis 10y ago
      Nope. See gurkendoktor's reply to me above. I agree with his/her reasoning.
- gurkendoktor 10y ago
  I actually enjoy having separate files for interface and implementation. It's a pain in C++ where you have to put your implementation details (instance variables) in the header, but in ObjC, headers are pretty clean. I've noticed that my Java-based coworkers often create well-documented interfaces with only a single implementation. They claim to do it for testability, but Mockito can deal with concrete classes as well - I suspect that they secretly enjoy looking at 10 lines of code that describe what a class does :)
gurkendoktor 10y ago
I love ObjC, it's the epitome of pragmatism. Fantastic compatibility with C/C++, malleable enough for GUI glue, wonderful libraries (I love NSCalendar & friends). My clients still accept ObjC for new projects, and they'd be crazy not to, considering how much the Swift 3 migration has cost early adopters. Given my current pessimism about Apple technologies, I think I'll just milk my ObjC skills until everyone goes Swift-only and then look for work in a portable programming environment.

pohl 10y ago

Objective C will always have room in my heart, but I'll never go back to it. There's too much .h ceremony.

sdegutis 10y ago
Meh, I've spent about 20 hours on this project so far, and I'd estimate probably 2 minutes of that time was spent managing .h files.
- yoz-y 10y ago
  Do you have any concerns about maintainability? So far Apple has been advancing Obj-C interfaces along with Swift, but time will probably come when some new OS features will only be available through Swift.
  - sdegutis 10y ago
    Nope. See gurkendoktor's reply to me above. I agree with his/her reasoning.
gurkendoktor 10y ago
I actually enjoy having separate files for interface and implementation. It's a pain in C++ where you have to put your implementation details (instance variables) in the header, but in ObjC, headers are pretty clean. I've noticed that my Java-based coworkers often create well-documented interfaces with only a single implementation. They claim to do it for testability, but Mockito can deal with concrete classes as well - I suspect that they secretly enjoy looking at 10 lines of code that describe what a class does :)

gurkendoktor 10y ago

I love ObjC, it's the epitome of pragmatism. Fantastic compatibility with C/C++, malleable enough for GUI glue, wonderful libraries (I love NSCalendar & friends). My clients still accept ObjC for new projects, and they'd be crazy not to, considering how much the Swift 3 migration has cost early adopters. Given my current pessimism about Apple technologies, I think I'll just milk my ObjC skills until everyone goes Swift-only and then look for work in a portable programming environment.