iOS Objective C vs Swift

[1458279]

Interesting, you think it would work? but the updating of the swift syntax just scares the hell out of me.


I'm going through hell right now, working 9AM-2AM visiting the customers during day and working at night with the india office (only 4 guys in USA now, 2 in LA, 2 IN NYC)

Version control is an issue, i mean simple grammar mistakes, cosmetics, no close button if you open something (just an example of the scenarios)

I mean it was just crazy, spaghetti code in our iOS and I have to support our ERP system customers, EDI, wholesale website, retail website, retail app , itradeshow app. All of which is a good foundation and good database with web services, but boy does the front end of everything needs work.


I'm losing my mind and I'm fighting day and night against swift with the owner/boss. because it stalled development for 2 years maintaining it. I mean not completely but we wasted the majority of the time updating swift and testing making sure the functions we already have worked.


Not to mention there isn't much swift help on the internet (might be more now), what should i do? We're undermanned as it is and its very hard to explain business logic to our indian programmers.

And we sell software to the fashion business with all those sizes, reports, shipping scenarios.

At this point I'm just venting, but yeah dude you really think so? Based of my experience my overseas iOS team is going to spend half the time learning.

I feel your pain. I've been there. Even with a small team on a med sized project it can be a nightmare. So many little things to check. I had one change cost me a client because the product had a little quirk in it and the client's don't care about your problems, they just want a product that works.

This goes back to an analysis of the benefit vs the costs as well as are we being force in one direction, which seems to be the case as we see ObjC not getting updates.

 

[AxoNeuron]

Honestly I would start looking for a new job. I've had to work with some junior Indian programmers before, they're not bad people but wow, they pump out some truly awful code.

If you can find another job offer, I would give your current boss an ultimatum, either give up on their current idiotic strategy, or find a new programmer.

 

[PizzaBoxStyle]

The whole "++" not going to work anymore is a joke. Other languages use it and it's a standard, if someone can't use it properly, they shouldn't program. What value would they have in any other language, and what value is there in a programmer that only knows one language that only works on one platform?

If you can't handle X++ or ++X, why program at all?

I think it's funny that pre/post-increment operators are bad because they require people to learn how to use them, but you are considered a backwards curmudgeon who doesn't want to learn anything new if you are critical of Swift.

 

[1458279]

I think it's funny that pre/post-increment operators are bad because they require people to learn how to use them, but you are considered a backwards curmudgeon who doesn't want to learn anything new if you are critical of Swift.

HA! Good catch, didn't see that

 

[JasmineJasmine]

But why does Apple go out of its way to make life difficult with another darn language. Why not stick with Java syntax or in even a version of c++ - keep just the good bits if you have to! But a new language - life is short enough without wasting it on another wannabe language!
[doublepost=1456242192][/doublepost]A web based Mac like MacinCloud.com is an option or a Virtual Machine on your PC. Both can be very limiting and slow depending on your network connection or how fast your PC is. I don't recommend either approach as both get in the way and are sluggish. Your best bet is to borrow a Mac from a friend (2008+), buy a used Mac (eBay/craigslist), or buy refurbished Mac from Apple.

 

[1458279]

But why does Apple go out of its way to make life difficult with another darn language. Why not stick with Java syntax or in even a version of c++ - keep just the good bits if you have to! But a new language - life is short enough without wasting it on another wannabe language!
[doublepost=1456242192][/doublepost]A web based Mac like MacinCloud.com is an option or a Virtual Machine on your PC. Both can be very limiting and slow depending on your network connection or how fast your PC is. I don't recommend either approach as both get in the way and are sluggish. Your best bet is to borrow a Mac from a friend (2008+), buy a used Mac (eBay/craigslist), or buy refurbished Mac from Apple.

I think you posted the 2nd half in the wrong place

As far as why Apple did this, it seems that Apple wanted to attract the next gen of programmers.
There's been a steady stream of new programmers getting into iOS and ObjC was too much for most of them. Apple doesn't want to share developers, they want Apple developers to make the best killer apps because that's the next big thing to keep sales up for Apple.

Apple actually paid one game company to delay their release on Android yeas ago.

They've really pushed Swift and it seems it was half baked, so they must have been in a hurry to do something about developers going over to Android.

The world had a lot of C++/Java programmers before the iPhone. Apple had the lead device for a while but when the market expanded, many went to Android. Android development sucked, but they can change that.

Soon the devices will look more and more alike. Apple can't claim the Android phones are junk, they want to claim their apps are junk but that can't last forever.

 

[firewood]

But why does Apple go out of its way to make life difficult with another darn language. Why not stick with Java syntax or in even a version of c++ - keep just the good bits if you have to! But a new language - life is short enough without wasting it on another wannabe language!

Improvement requires change (both on Apple's part to create, and on the developer's part to learn newer better methods). Java is owned by Oracle and has had problems (security, size and performance). Objective C was already Next's opinion of just the good parts of C++ OOP. But both are fairly old languages (C++ around 4 decades old, Java around 2 decades old).

Very few people use 20 year old computers for professional development (mostly just for playing around, historical education, and "demo-scene" performances). And it's very hard to keep 40 year old computers just in running condition. Why use a programming language just as old?

 

[PizzaBoxStyle]

Objective C was already Next's opinion of just the good parts of C++ OOP.

Don't think so.

Objective-C is Smalltalk built atop C. And according to Wikipedia, both Objective-C and C++ appeared around the same time.

JavaScript is nearly as old as Java. Does that mean that we should stop using JS too?

 

[eventailapp]

As an experienced C++ programmer I would say that Swift is much more pleasant to write. Mainly because first class function are only an afterthought and an extremely modular approach nature of C++.

JavaScript is nearly as old as Java. Does that mean that we should stop using JS too?

Some would say yes. And the fact that there are so many languages that compile to JS is quite a statement. Personally I have hopes that ES6 will bring the language up to speed.