This,
Swift is easy, but I'm not sure if we should go through with it but the Company Owner is just pushing everyone to swift.
But its some what unstable (bugs in flight test, certain things here and there like light weight core data migration) makes things a living hell.
and there isn't as much help online as much as there is for OBJ-C, not to mention when hiring developers, the owner wants "swift" developers.
But whats the difference as long as it gets the job done? and if it bloats the software obviously that isn't something we would want to do and something i didn't know of.
Our iOS apps are secondary to our main system, but its driving me nuts because, we don't have an army or a department of developers.
Is it safe to just develop in OBJ-C for now? I really don't see the real reason to develop in swift, although i really see the advantages of it.
I hear that almost everyone is going to adopt swift? but I'm not sure.
Concerning app size: From: http://swiftiostutorials.com/swift-application-size-unexpected-pitfall-swift/
However, for my amusement this application was bigger for iOS and not only a few kilobytes, but 3.4 times bigger!
App download size is a big factor as memory (esp on Apple devices) isn't cheap and apps continue to grow in size.
The "Swift is easy":
ObjC is certainly a "different" language. For some 30 years, I've done everything from COBOL to C++, and can't say I would have made ObjC the way it is.
However, easy is only one aspect of programming. Someone showed me some advanced Swift code vs the same ObjC code and ObjC was much more straight forward.
I can do blocks easily in ObjC (odd syntax, but easy), I showed this to someone learning Swift, and they didn't get it at all.
Point: the basics of the "language" is mostly to control API calls. There wasn't anything "wrong" with ObjC and it has huge support. Introducing a new language that's like no other, is a real risk.
What exactly is the expected gain for a company that has advanced apps in ObjC to switch?
It seems more of a play to get more newbees into the app dev group. We really don't need more app developers, we need higher quality apps. Most app users only use a VERY small number of apps. We need advanced apps, which are made by advanced developers, not new comers to a game that's long been underway.
As far as safe for ObjC, as long as there's a compiler that supports it, it'll be safe. I don't know if Apple can ax it like it were 32 bit apps or non-retina apps. Again, most of the app is the API calls and control of those calls.
Remember, MicroSoft was one of the most powerful tech companies in the world, they pushed several things, yet many businesses were still running WindowsXP. Simply because it worked.
In the end, the customer doesn't know or care what language an app is written in. They just see what it does and how fast it does it.
It's interesting that Apple went with a NEW language instead of adding support for multi-platform solutions. Why would they do that? They are clearly protective of their system, they paid some developers to NOT release on Android. Most of the smart phone market remains untapped (Asia). If apps were runnable on any device, Apple would lose some market share, they can't afford to let that happen.
Can anyone explain the gain of stopping what we have now and starting over with a new language? Will the end product be that much better? With the user even know the difference? (other than 3.5X bigger download)
When you take your car in for repair, do you car what brand tools are used? No, you just care about the cost, quality, and how long it'll take.
I'm not against learning, I've learned many languages, but my time is better spent mastering all the new API and 3rd party code and making better apps. I don't see how Swift helps anything.