I've been fighting tooth and nail with the senior developer/owner of our company. He developed with swift, which i advised against because it was a new language and unstable and constantly changing and getting updated. He brushed my concerns aside and said "if we don't go swift no we never will, it so much better and easier to code" But i really so no REAL need besides it being simpler to code. The fact is now, we always been over swamped with work, we don't even have time to take care of deprecated crap on our old versions of our source code for all of our apps. Now we have to update the swift everytime, nobody in our company knows swift besides this senior developer, who isn't experienced with swift anyways. As in he has a lot of experience in programming but when he's coding in swift he doesn't know what he's doing (memory leaks, problems in the future regarding core data migration, i mean a whole bunch of things) The only person who knows even a little bit of swift is a junior programmer who was a power builder programmer that was forced to learn swift. I do not trust this guy with anything. Right now its making a 1 min job of changing a logo and recompiling and uploading to the App Store or installing it on a device to a 2-4 day job. Because of extensive testing, We do E-Commerce/Order taking apps. So numbers have to be perfect, can't lose orders because of crashes, SHOULDN'T be crashing because OUR customers use this to take orders for THEIR customers, so if it crashes not only is it embarrassing for us, but its embarrassing for OUR customers. My question is is there any REAL benefit to swift. I suggested why not save swift for version 2.0, i really don't see the need and really worried about that stability of the app if we implemented swift. Common sense tells me NO from day one, Why are we implementing swift into our already existing source code that is stable that we are selling to our customers. Sometimes i need to do on field emergency installations, or maybe i have to test with a customers database that i haven't seen for 1 year. This delays everything, and when we update coding I'm afraid its gonna mess it up. Especially when 1. we don't know swift. 2. we don't have time to do a full test everytime swift gets updated 3. there is just NOT enough HELP with swift i can find online. Its just extremely difficult. I was trying to find out and issue with Lightweight Core Data Migration with swift If we just sticked with OBJ-C it would never would of happened, no extreme need to update code (i can still compile) My Question is, is there a real need to go to swift? What the Senior developer says is "if we don't go to swift now, we never will" But if we do it on version 2, we eventually will. But right now we don't have the skills to program in swift nor the time to really learn it because of pending projects, modifications, bug fixing, and basic maintenance. It drives me crazy, because there are multiple versions of this ONE app because of the database differences between each customer. and to update each customer with the latest source code of our app is also as tedious because of the different databases they use (they have an older database and main system program (ERP)) Regardless, i hate a huge discussion/argument and pointed out all these faults and he agreed to convert version 1 back to OBJ-C hesitantly. Am I wrong? Is there real use for swift right now? Because its just an extreme burden since we don't even have the time or man power to update swift. and things go wrong on the field like at the trade shows or showrooms, so we need to be able to make emergency fixes and installations and compile. Appstore uploads as well if theres a copyright issue with the logo. None of them we can address immediately because of this problem. I'm just really sick and tired of telling our customers "sorry" "this is going to take a week" "we can't do this right now" When its basic support that they SHOULD receive but we can't give it to them because of this swift issue. Its literally something in our control, because if we didnt go with OBJ-C we wouldn't have this issue in the first place and we can just have more time to allocate to more important tasks.