Hi,
I'm not a ranty person so I never actually thought I'd post anything here but here it goes.

From the beginning.
We use ancient technologies. PHP 5.2, Symfony 1.2 and a non RFC complient SOAP with NO documentation.
A year ago We've been thrown a new temporary project. An VOIP app for every OS.
That being iOS, Android, MAC, PC, Linux, Windows mobile. With a 3 month deadline. All that thrown at 4 PHP developers. The idea being that They'll take it, sign the delivery protocol, everyone happy. No more updates for the app needed. They get their funds they needed the app for and we get paid.

Fast forward to today...

Our dev team started the year with great news that We'll most likely have to create a new project. Since the amount of new features would be far greater than current feature set, we managed to finally force our boss to use newer technologies (ie. seperate backend symfony4 PHP7+/frontend react, rest api and so on). So we were ecstatic to say the least. With preestimates aimed at a minimum 3 month development period. Since we're comfortable with everything that needs to be done.
Two days later our boss came to me that one of our most annoying clients needs a new feature. Said client uses ancient version written on a napkin because They changed half of the specification 2 weaks before deadline in a software made not by a developer but some sysadmin who didn't know anything. His MVC model was practically VVV model since he even had sql queries in some views. Feature will take 3 days - fixing everything that will break in the meantime - 1-2 months.
F*** it, fine. A little overtime won't kill me.
Yesterday boss comes again... Apparently someone lost a delivery protocol for a project we ended that half a year ago. Whats even better at the time when we asked for hardware to test we never got any. When we asked about any testing enviornment - nothing. The app being SEMI-stable on everything is an overstatement but it was working on the os'es available at the time. Since the client started testing now again, it turns out that both Android app does not work on 8.1/9 and the iOS app does not work on ios12. The client obviously does not want to pay and we can do little with it without the protocol, other than rewriting the apps.
It will take months at least since all of those apps were written by people that didn't know neither the OS'es nor the languages. For example I started writing the iOS one in swift. Only to learn after half of the development time, that swift doesn't like working by C Library rules and I had to use ObjC also. With some C thrown in due to the library. 3 unknown languages, on an unknown platform in 3 months. I never had any apple device in my hand at that time nor do I intend to now. I'm astonished it worked out then. It was a clusterf**k of bad design and sticking everything together with deprecated apis and a gum. So I'll have to basically fully rewrite it.

If boss decides we'll take all those at the same time I'll f***ing jump of a bridge.

Ad an Android dev, I hate that hybrid solution like cordova, react native or similar frameworks. Companies sell their apps for ridicolous prices, so every native Android/ios dev need to get it's work faster and for a lower price.
Customers can't understand that hybrid app are faster to create but works worse. I'm hating you, hybrid-guys

Meme Convos with @svc64 2: Electric Boogaloo

So, a company recruted me as an hybrid developer (ionic), they affected me to the mobile team where all they talk about there is either Java or ObjC ... I feel "alone" there, being the only one who knows JS and web techs in general, i sometimes join the web team at lunch time so we can talk in "commun" knowledge in JS frameworks and stuff i know :v

Spent an entire week working on XCode configurations for a react-native+swift+objc bridging project. Been failing builds all week. Finally i look over to see the glorious word Succeeded!

Then I realized it was the clean that succeeded, not the build. FFS

Trying (for fun) to run a GNUStep Obj C program that calls c headers has proven something to me:
I really do not know what I am doing with makefiles and should probably slowly and respectfully walk away to continue doing what i was doing in c++

Kids, documentation reading is important.

I also do happen to really like objc

The senior iOS dev I was working with in my first job after uni - he showed me so many objc tricks and his self-written libraries to make working with UI stuff in swift more concise, it blew my mind. At the same time, he was very humble and calm, and had a funny humor at times. Also his code and the architecture in an older app we needed to work on was super easy to read and understand. That's why I want to be more like him - and eventually grow a beard :-)

An interns excuse to not do work, "I'm a Java developer, not objc" are you really even a Dev at all smart ass?

as! much! as I like it better? than @objc!, sometimes! I want! to punch! the hipsters that created? Swift

Wow..so i decided to try out Swift instead of always writing in ObjC while writing a native module in my React Native project.
I spent a fucking hour trying to figure out how can i write code to get a value from my info.plist in Swift and what i got was a humongous piece of code whereas ObjC does it in one line.

Whats the hype about Swift?!? Its the worst fucking language out there

I learned to code on a jailbroken iPod touch around 2009. I wanted to compile some random project for jailbroken devices, but I had a windows comp (with dialup!!!), so I was like "why not do it on the iPod itself?". I didn't even have wifi, so I'd sneak out of my parents' house at night and steal the neighbor's (hey, I was 11 w/ overprotective parents who would freak out if I occupied the phone line w/ internet) to go read up on compilers, jailbreaking, etc etc. Eventually I got a working compiler and toolchain, but when I went to compile the project I wanted to use (and not just a test project that I found), it spat out errors. So I learned C/ObjC on my iPod. Turned out the project I was trying to compile was a load of BS, so I implemented my own version and put it on github. From a fuckin iPod. Win. It was some SBSettings control. Once upon a time, you had to jailbreak to get those cool slide up/down menus with the toggles for wifi, bluetooth, location, etc!!!

Wish the Objective-C compiler had better type checking. There's no reason for it to not error out when I'm migration a property from one type to another.

Me and @asafniv cannot settle this argument and we need your conclusion.

What syntax makes more sense, Objective-C or Swift?

In my opinion, Swift's syntax is better than Objective-C, but Asaf's opinion the the opposite.

We failed to settle this argument and that is why we need YOU to give us your opinion.

In the comments I will send 2 identical functions, one is written in Objective-C, and one is written in Swift.