3 ms·

And I thought 2017 is the year when I start a new app in swift... guess will be sticking to objc and react native depending on what makes sense where.

andreasley 9y ago
Just give it a try. While Swift is not perfect, it really is great for macOS/iOS development and continuously getting better. I'd never go back to ObjC.
leeter 9y ago
as much as I like swift, wait for it to become stable. Don't subject yourself to the pain yet. That said do take advantage of using literally all the things that have been added to Objective-C for compatibility as they provide useful information and diagnostics.
- valuearb 9y ago
  It is stable. I would wager that more people are building professional apps in Swift today than Objective C.
  - sheeshkebab 9y ago
    While renaming for loops? Even js is more stable than this...
nicky0 9y ago
I'm with you. I see few advantages of switching my large existing codebase to swift, only disadvantages. Maybe in a few years the balance will change.
- orbitur 9y ago
  > I see few advantages of switching my large existing codebase to swift There are none. Don't transition an existing, stable ObjC project. I don't understand why this is a thought anyone would entertain, especially since ObjC itself isn't going anywhere. If you are starting a new project in Swift and it will be pure Swift, that's fine. Go for it. Do not attempt to migrate existing ObjC projects or use Swift in them.
pvinis 9y ago
I am actually working on a react native app with native modules in objc, swift, and a combination of the two. It is stable and easy to work with all three. Just use what you want to use. You wanna make it full swift, go for it. React native, go for it. Stick with objc you know, go for it. No wrong choice here. ps: Well, maybe pure objc is not the best choice, since it's on its way out, but it's a long way to its end.

andreasley 9y ago

Just give it a try. While Swift is not perfect, it really is great for macOS/iOS development and continuously getting better. I'd never go back to ObjC.

leeter 9y ago

as much as I like swift, wait for it to become stable. Don't subject yourself to the pain yet. That said do take advantage of using literally all the things that have been added to Objective-C for compatibility as they provide useful information and diagnostics.

valuearb 9y ago
It is stable. I would wager that more people are building professional apps in Swift today than Objective C.
- sheeshkebab 9y ago
  While renaming for loops? Even js is more stable than this...

nicky0 9y ago

I'm with you. I see few advantages of switching my large existing codebase to swift, only disadvantages. Maybe in a few years the balance will change.

orbitur 9y ago
> I see few advantages of switching my large existing codebase to swift There are none. Don't transition an existing, stable ObjC project. I don't understand why this is a thought anyone would entertain, especially since ObjC itself isn't going anywhere. If you are starting a new project in Swift and it will be pure Swift, that's fine. Go for it. Do not attempt to migrate existing ObjC projects or use Swift in them.

pvinis 9y ago

I am actually working on a react native app with native modules in objc, swift, and a combination of the two. It is stable and easy to work with all three. Just use what you want to use. You wanna make it full swift, go for it. React native, go for it. Stick with objc you know, go for it. No wrong choice here. ps: Well, maybe pure objc is not the best choice, since it's on its way out, but it's a long way to its end.