When a hiring manager wants 5+ years experience in Swift.

Swift release date = June 2, 2014

😂👍🖕

Swift 😐

Oh Swift why

Trying to teach coding to a kid:
Kid: Can you teach me XCode?
Me: No but I can teach you Swift or Objective-C
Kid: But I want to learn to code in XCode
Me: Yes you will code in XCode but I will teach you swift
Kid: My dad said that you actually know how to code but apparently not.

Client: "Users are still facing the same problems as before"

Me: "Did they update the app?"

Found this in 9gag. I personally haven't done Swift.
See you in 5 years mate.

Tonight: Learning Swift while listening to Taylor Swift.

Swift, oh my god, why do you have to be like this?

I'm looking to write a simple for loop like this one in java

for(int i = 5; i > 0; i--) {
// do shit
}

Thats it, simple, go from 5 to 1 (inclusive), I saw that to iterate over a range in a for loop (increasing ordeR) I can do this

for i in 0...5 {
// do shit.
}

So I thought maybe I could do this to go in reverse (which seems logical when you think about it doesn't it?)

for i in 5..<0 {
// do shit
}

But no, this compiles FINE (THIS IS THE FUCKING KICKER IT COMPILES), alright, when you the code runs you get a fucking exception that crashes the mother fucking application, and you know what the problem is?? This dogshit, shitStain of a language doesn't like it when integer that the for loop starts with is larger than the integer that the for loop ends with MOTHERFUCKER ATLEAST TELL ME THAT AT COMPILE TIME AS A MOTHERFUCKING WARNING YOU PIECE OF SHIT!!

Alright *deep breathing*, now we can't just be stuck on this raging, we're developers need to move forward, so I google this, "Swift for loop in reverse" fair enough I get a straight forward answer that tells me to use the `stride` functionality. The relevant code for it

for i in stride(from:5 to:1 by:-1) {
// do shit
}

Wow looks fine and simple right?? (looks like god damn any other language if you ask me, no innovations here piece of shit apple!) WRONG BITCHES !!! In the latest version of Swift THE FUCKING DEVELOPERS DECIDED TO REMOVE STRIDE ALTOGETHER, WITHOUT ADDING IN A GOOD REPLACEMENT FOR THAT SHIT!

Alright NOW IM FUCKING MAD, I got rage on stackoverflow chat, a guy who's been working on ios for quite a while comes up n says and I quote
"I can sort of figure it out, but besides that, iterating in reverse is uncommon enough that it probably hasn't crossed anyone's mind."

Now hope you guys understand my frustration, and send me cookies to calm me down.

Thank you for listening to me !

My map generator(rewritten in swift) produced its finest continent... after 40 minutes...

My life as an ios developper

Haha. Waiting to see how this will go

Poopy function in Swift

Hello world, this is my first rant :)

Today at work, this was on the whiteboard.
Little "war" between the iOS pole and the PHP pole :D (Obviously PHP is better)

I think they are looking for time travelers..

My Chrome tabs everytime I try something with Swift.

IntelliJ sounds like Taylor Swift

Wow, my girlfriend has been really efficient wrapping and organising the presents under the tree... You could say she’s a Swift Package Manager!!

My first experience with Swift ended in me infecting myself with a virus (kinda). I wanted to create a macOS app that would listen for a global key event, catch it and then type a word.

During development I set it up to listen for ANY key event and to type "BALLS". So what happened? I compiled the code, everything looked good, I started the app and pressed a key which emitted a key event. The event was caught by my app and it typed "BALLS", just as expected. However, the typing of the word caused a NEW key event to be emitted, which the app also caught. The infinite loop was a fact. FUCK!

I tried closing down XCode but all I could see was "BALLS BALLS BALLS" everywhere. I tried everything I knew but it just kept typing "BALLS". I had to hold down my power button to make it stop.

I finally finished the app (which I named "The Balls App", I kept the word "BALLS"). I solved this issue by only listening for KeyUp and when emitting the "BALLS" word I just used KeyDown.

Someone at Apple truly is a genius.

I know python , JS, java etc. Some might know php, some others might swift and so on.. but the only language understood by everyone all over the globe is this 😂(wait for it to load, and you will believe what I'm saying :P )

Shake it off...

XCode = Expect the unexpected!

Holy moly..

Working on my MacBook and out of nowhere: *click* dead..

Try to restart it, fan spinning for a second, then: nothing.. recovery mode. Nothing..
FUCK!!

Doing research on my iPhone.. see Louis rossmann had a case like this in which one foot of the clock on the main board doesn’t have connection.

But I don’t have the right tools to open the MB..

I turn it around, shake it shake it shake it shake it baby like Taylor swift, knock on the back, knock on the keyboard and voila.. working again😪

Didn’t think that still works with modern technology..

Getting the nth character of a string.

Every other language:

string[n]

Swift:

string[index(string.startIndex, offsetBy: n)]

Function definition in various programming languages

//JavaScript/PHP

function myfunc()
{

}

//Swift

func myfunc()
{

}

//Kotlin

fun myfunc()
{

}

//Rust

fn myfunc()
{

}

//Next...

f myfunc()
{

}

Updating from Swift 2 to 3 using Xcode's "migration assistant"

Hopefully it's written in Swift!

!rant

I will read through all of youuuuuuuu lol

"if it compiles, it works"

A couple of years ago (2015)...

Me: If i'm going to develop iOS Apps i need a Mac, big screen, etc...
Boss: Ok...

A few days go by...

Boss: Ok, we've ordered a Mac already
Me: good.
Boss: It's that small one, will be ok...
Me: <Check mac models and wonder the implications of "small">
Boss: It's the cheapest one plus a 21 inch monitor. Keyboard and Mouse you already have...
Me: <incredulous> At least order a mac keyboard...

Time goes by... Boss comes to discuss something about the app... i change something and check on the emulator (yes no real devices...) and boss complains:

Boss: Incredible, this machine is so slow...
Me: <throws a shrug>

Conclusion... still developing on this machine... damn.. i can read a newspaper every now and then while waiting for the machine to comply...

Fml...

Would you still be a programmer if CTRL-Z didn't exist?

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.

Stack Overflow, always reliable

Today am migrating an app from Swift 2 to Swift 3.
Brace yourselves for some murder rants.

When the last dev wrote code and you dared to read it....switch on a Boolean, what even is your life legacy dev?

First thing to do after downloading swift for linux is to obviously place the folder inside another folder named Taylor

Fuck dates and fuck date manipulation. Even when I think I get it right, I don't

If you ever use emojis for variable naming, please do a favor for the whole developer community by formatting your hard drive twice and then never touching a computer again - because you're an idiot.

Seriously though, why Apple? This screenshot is from the official Swift Language documentation...

Another day with xcode

Even Apple believes that Xcode suggestions are not reliable... 😂😂😂

(From App Development with Swift book in iBooks Store from Apple)

And finally my new setup for coding swift 😂✋💻

swift might be coming to android

personally I think it would be awesome to have one common language for mobile development that isn't just some hack or patchjob like some other projects are

what do you guys think?

Learning Swift and a Timer as first Application. ;)

Thanks Apple to not natively supporting hex colors in Swift! That would be too convenient I suppose...

Damn, my boss added me to a "almost" complete protect with a bunch of spaghetti code in a language that I don't know more than the syntax of for loops and declaration of variables (swift) ..... I'm really fucked

Made my first ever app for iOS using Swift. I must say I kinda like this programming language.

Came into this company as a web dev. Now I have to develop a native iOS app in swift.

FML

Just started learning swift and iOS development. OMG I fucking hate it so much.

When a new swift version is released and it breaks my apps.

Leaving swift be like....

Holy shit. I just watched a video on Rust and I think I am in love.

Tracked mutability, reference counting, guaranteed thread safety, all in a compiled type-safe language with the performance of C++? 😍

Why did I not check this out sooner??

Theres a debate in my company about whether or not to be using RxSwift on iOS apps. I'm not 100% convinced. Today we had two submissions for a coding challenge come in. One uses nearly all the same Rx modules this company does, one was vanilla Swift.

Just by chance noticed the vanilla app writer contributed ~5k lines of code to the challenge overall. Including libraries, the Rx one contributed ~45k.

That to me is just bat shit crazy. It would want to be the most amazing, time saving, bug reducing thing the world has ever seen to justify that volume of code.

As a web developer.. Me working on my first mobile app. :D

Well fuck you too Swift! Your mother is to complex to be solve in reasonable time!

"A comment isn't needed if the name is good and the responsibility is clear" - M.Howell

Sitting on my porch, drinking liquor, trying to write an iOS app. I've been reading error messages and swearing for over two hours. If I have neighbors, they probably think I'm performing a black sacrament over here

Maybe I actually am?

Dear Apple, why not make Swift good instead of a piece of shit? Just a thought.

Every language ever:
"You can't compare objects of type A and B"

Swift, on the other hand:
"main.swift:365:34: note: overloads for '==' exist with these partially matching parameter lists: (Any.Type?, Any.Type?), ((), ()), (Bool, B ool), (Character, Character), (Character.UnicodeScalarView.Index, Character.UnicodeScalarView.Index), (CodingUserInfoKey, CodingUserInfoKey ), (OpaquePointer, OpaquePointer), (AnyHashable, AnyHashable), (UInt8, UInt8), (Int8, Int8), (UInt16, UInt16), (Int16, Int16), (UInt32, UIn t32), (Int32, Int32), (UInt64, UInt64), (Int64, Int64), (UInt, UInt), (Int, Int), (AnyKeyPath, AnyKeyPath), (Unicode.Scalar, Unicode.Scalar ), (ObjectIdentifier, ObjectIdentifier), (String, String), (String.Index, String.Index), (UnsafeMutableRawPointer, UnsafeMutableRawPointer) , (UnsafeRawPointer, UnsafeRawPointer), (UnicodeDecodingResult, UnicodeDecodingResult), (_SwiftNSOperatingSystemVersion, _SwiftNSOperatingS ystemVersion), (AnyIndex, AnyIndex), (AffineTransform, AffineTransform), (Calendar, Calendar), (CharacterSet, CharacterSet), (Data, Data), (Date, Date), (DateComponents, DateComponents), (DateInterval, DateInterval), (Decimal, Decimal), (IndexPath, IndexPath), (IndexSet.Index, IndexSet.Index), (IndexSet.RangeView, IndexSet.RangeView), (IndexSet, IndexSet), (Locale, Locale), (Notification, Notification), (NSRange,

NSRange), (String.Encoding, String.Encoding), (PersonNameComponents, PersonNameComponents), (TimeZone, TimeZone), (URL, URL), (URLComponent s, URLComponents), (URLQueryItem, URLQueryItem), (URLRequest, URLRequest), (UUID, UUID), (DarwinBoolean, DarwinBoolean), (DispatchQoS, Disp atchQoS), (DispatchTime, DispatchTime), (DispatchWallTime, DispatchWallTime), (DispatchTimeInterval, DispatchTimeInterval), (Selector, Sele ctor), (NSObject, NSObject), (CGAffineTransform, CGAffineTransform), (CGPoint, CGPoint), (CGSize, CGSize), (CGVector, CGVector), (CGRect, C GRect), ((A, B), (A, B)), ((A, B, C), (A, B, C)), ((A, B, C, D), (A, B, C, D)), ((A, B, C, D, E), (A, B, C, D, E)), ((A, B, C, D, E, F), (A , B, C, D, E, F)), (ContiguousArray<Element>, ContiguousArray<Element>), (ArraySlice<Element>, ArraySlice<Element>), (Array<Element>, Array <Element>), (AutoreleasingUnsafeMutablePointer<Pointee>, AutoreleasingUnsafeMutablePointer<Pointee>), (ClosedRangeIndex<Bound>, ClosedRange Index<Bound>), (LazyDropWhileIndex<Base>, LazyDropWhileIndex<Base>), (EmptyCollection<Element>, EmptyCollection<Element>), (FlattenCollecti onIndex<BaseElements>, FlattenCollectionIndex<BaseElements>), (FlattenBidirectionalCollectionIndex<BaseElements>, FlattenBidirectionalColle ctionIndex<BaseElements>), (Set<Element>, Set<Element>), (Dictionary<Key, Value>.Keys, Dictionary<Key, Value>.Keys), ([Key : Value], [Key : Value]), (Set<Element>.Index, Set<Element>.Index), (Dictionary<Key, Value>.Index, Dictionary<Key, Value>.Index), (ManagedBufferPointer<Hea der, Element>, ManagedBufferPointer<Header, Element>), (Wrapped?, Wrapped?), (Wrapped?, _OptionalNilComparisonType), (_OptionalNilCompariso nType, Wrapped?), (LazyPrefixWhileIndex<Base>, LazyPrefixWhileIndex<Base>), (Range<Bound>, Range<Bound>), (CountableRange<Bound>, Countable Range<Bound>), (ClosedRange<Bound>, ClosedRange<Bound>), (CountableClosedRange<Bound>, CountableClosedRange<Bound>), (ReversedIndex<Base>, ReversedIndex<Base>), (_UIntBuffer<Storage, Element>.Index, _UIntBuffer<Storage, Element>.Index), (UnsafeMutablePointer<Pointee>, UnsafeMut ablePointer<Pointee>), (UnsafePointer<Pointee>, UnsafePointer<Pointee>), (_ValidUTF8Buffer<Storage>.Index, _ValidUTF8Buffer<Storage>.Index) , (Self, Other), (Self, R), (Measurement<LeftHandSideType>, Measurement<RightHandSideType>)"

why? just why???

Google being Google

Dear Swift, we have to break up. I’ve found a new language to love. Oh don’t act so surprised, you know our relationship was on shaky ground. You never let me have any fun. You’re always telling me what to do and how to do it and I’ve had enough. You treat me like a child, and I’m moving on.

Things were good in the beginning, and you may have impressed me with your automatic reference counting, but my new language can do that too, and so much more, and does it faster than you could ever imagine. You see unlike you, my new language doesn’t boss me around. It *trusts* me, Swift. That’s the one thing you never could understand. I need to be trusted; and know that I can trust in you.

Well I can’t. Not anymore, Swift. It’s over. My new language just treats me better than you ever could. I’m sorry it came to this but I deserve better than you Swift. We’ve both known this for a long time.

I wish you the best, but you probably shouldn’t call.

I’m with Rust now.

Does anybody know why java is brown in GitHub, html is red, objective-c is blue, and swift is yellow?

"/path/to/my/file.swift:143:34: error: cannot convert return expression of type 'String.SubSequence' (aka 'Substring') to return type 'String'"

Ah yes, I love it when Substring isn't String

After making great progress in Swift, I was advised to go back and learn Objective-C. 2hrs in I'm like...

Me: I've got this wonderful idea, I'll try it in swift
OSX: download the 4.47 GIGABYTE Xcode
Me: :'( ok
Xcode : you need to update your OS and that's again more than 4.5 GIGABYTE
Me : Sublime -> Main.class

iOS dev here
Just wanted to share my experience on updating Xcode and why I schedule 3 hours for this process.
So, updating Xcode via the AppStore has always been flaky at best and ofcouse Xcode needs to be closed first. You hit update, the button turns gray, half an hour in you still see no progress...
That's why I often just download it from the dev center. But since Xcode Ghost the app is also wrapped in a signed container.
So,
Downloading: 10 minutes
Expaning: 60 minutes!!!
After that I move the app in place and fire it up, always have to close my music player first grrr...
After that Gate Keeper verifies the app for another 60 minutes.
Finally Xcode comes to live.
Only need to install new command line tools for another few minutes and I can continue coding.
Wait. Half my day is over!
Why Apple? Why?
#wk24

Area of focus: Native iOS dev

Why: Spent years trying hybrid tools, dealing with the most ridiculous errors, bugs and issues you can begin to comprehend and then ... something magical happened. I got a book on Objective-c, learned a little, tried a simple app ... and it worked ... like properly worked, and on all the devices without taking half the RAM.

I'll say that again as I don't think it landed. In Objective-c, I got no issues where only the CEO's phone + OS version meant I couldn't load a map and a pin (looking at you titanium!!!)

In Objective-c, I wasn't promised storyboards and autolayout, only to find out they are completely different, and may god help you trying to google the issues, as the only ones to show up would be the native tools (looking at you Xamarin)

In Objective-c, my app doesn't instantly consume 125mb of RAM to load a fucking webview (looking at you ... well nearly every other hybrid tool)

... it just works. Then Swift came along and things only got better.

I FUCKING HATE SWIFT
THE SAME CODE DOESN'T COMPILE

I’m a long time Objective-C and Swift developer...I’ve been asked to “research” a project using React Native.

It felt dirty to be writing an iOS app using JavaScript.

I’m still not sure why and how React Native is better/faster than native Swift.

Someone change my mind...

A job on monster.com:
Wants 5+yrs of experience on Swift.
Swift just came out 3 years ago

When you start a new job as the only iOS Software Engineer, and after 3 weeks your boss constantly asks “well, how long is that going to take?” ...
I really wish my response could be “as long as it takes you to find another iOS Engineer for me to work with” 🤬

Oh dear Apple,

so you're telling me that for the camera API, the requestAuthorization() method returns a bool and for the PhotoLibrary it returns an enum. Why are you going with an enum when there are 2 states and the camera api doesn't use an enum?

(The 2 methods serve the same purpose, the enum exists in the camera api as well and has the exact same states)

And why do I need access to users photos, if I only want to write photos?

When you're writing unit tests in xcode and it crashes and loses its syntax colouring and autocomplete. All of a sudden you're coding on textedit instead.

The first two stories on slashdot's homepage are:
1. Google releases Angular 2, breaks backwards compatibility
2. Apple releases Swift 3, breaks backwards compatibility

If you use either of those tools, why do you put up with this? When did software engineering stop being about building useful or enjoyable things for our customers, and start being about doing thankless make-work for Silicon Valley billionaire companies? Is this the legacy we want to leave to the world?

Getting beaten up over the quality of an app i'm working on with 6 interns. We have a bunch of unit tests, was shocked to see so many issues ... until I looked at the tests.

A function returning a non-optional array has 1 check ... that the return value is not nil ... fml

People refusing to learn an improved programming language or technology, because it might contradict to what they "already know" and you're just there mastering it and appreciating its advantages that you will never learn if you had a closed mindset.

For those of you iOS Swift developers, how long did it take to learn and have a decent app with database functionality, coming from a different programming language background?

The moments of life we live for are sometimes times that look like these. Gotta love em

'Cause the gamers gonna game, game, game, game, game
And the government is gonna overplay, play, play, play, play
Baby, I'm just gonna code, code, code, code, code
I code it off, I code it off
Hackers gonna break, break, break, break, break
And the fakers gonna fake, fake, fake, fake, fake
Baby, I'm just gonna code, code, code, code, code
I code it off, I code it off

This is my first and current Rant/story so here it goes, I've been working for a company for past 10months now, where i was interviewed on Java, then i was put into mobile development and started to build an app in swift (successfully finished it) after two months i was working on ARKIT(didn't build anything BIG mostly R&D), then started working on React-native and built an app from scratch using firebase as backend (both RN and firebase was new to me) and pushed it to AppStore and PlayStore, and currently i'm working on Flutter!.. At first it was pretty irritating switching frameworks and technologies but now i've become more positive about it and i look at it as an opportunity to learn new stuff :)

read a job requirement post says need programmer min exp about 4-5 years
language :- SWIFT,php
😂😂

!rant

Need some opinions. Joined a new company recently (yippee!!!). Just getting to grips with everything at the minute. I'm working on mobile and I will be setting up a new team to take over a project from a remote team. Looking at their iOS and Android code and they are using RxSwift and RxJava in them.

Don't know a whole lot about the Android space yet, but on iOS I did look into Reactive Cocoa at one point, and really didn't like it. Does anyone here use Rx, or have an opinion about them, good or bad? I can learn them myself, i'm not looking for help with that, i'm more interested in opinions on the tools themselves.

My initial view (with a lack of experience in the area):

- I'm not a huge fan of frameworks like this that attempt to change the entire flow or structure of a language / platform. I like using third party libraries, but to me, its excessive to include something like this rather than just learning the in's / out's of the platform. I think the reactive approach has its use cases and i'm not knocking the it all together. I just feel like this is a little bit of forcing a square peg into a round hole. Swift wasn't designed to work like that and a big layer will need to be added in, in order to change it. I would want to see tremendous gains in order to justify it, and frankly I don't see it compared to other approaches.

- I do like the MVVM approach included with it, but i've easily managed to do similar with a handful of protocols that didn't require a new architecture and approach.

- Not sure if this is an RxSwift thing, or just how its implemented here. But all ViewControllers need to be created by using a coordinator first. This really bugs me because it means changing everything again. When I first opened this app, login was being skipped, trying to add it back in by selecting the default storyboard gave me "unwrapping a nil optional" errors, which took a little while to figure out what was going on. This, to me, again is changing too much in the platform that even the basic launching of a screen now needs to be changed. It will be confusing while trying to build a new team who may or may not know the tech.

- I'm concerned about hiring new staff and having to make sure that they know this, can learn it or are even happy to do so.

- I'm concerned about having a decrease in the community size to debug issues. Had horrible experiences with this in the past with hybrid tech.

- I'm concerned with bugs being introduced or patterns being changed in the tool itself. Because it changes and touches everything, it will be a nightmare to rip it out or use something else and we'll be stuck with the issue. This seems to have happened with ReactiveCocoa where they made a change to their approach that seems to have caused a divide in the community, with people splitting off into other tech.

- In this app we have base Swift, with RxSwift and RxCocoa on top, with AlamoFire on top of that, with Moya on that and RxMoya on top again. This to me is too much when only looking at basic screens and networking. I would be concerned that moving to something more complex that we might end up with a tonne of dependencies.

- There seems to be issues with the server (nothing to do with RxSwift) but the errors seem to be getting caught by RxSwift and turned into very vague and difficult to debug console logs. "RxSwift.RxError error 4" is not great. Now again this could be a "way its being used" issue as oppose to an issue with RxSwift itself. But again were back to a big middle layer sitting between me and what I want to access. I've already had issues with login seeming to have 2 states, success or wrong password, meaning its not telling the user whats actually wrong. Now i'm not sure if this is bad dev or bad tools, but I get a sense RxSwift is contributing to it in some fashion, at least in this specific use of it.

I'll leave it there for now, any opinions or advice would be appreciated.

*one bug*
Me: ohhhh got it !!
*fixes*
*23 bugs*
Me: ............

Someone at twitter forgot to unwrap an optional!

Why is it that whenever I show someone the app I made that they always suggest a bunch of fucking idiotic features. What is bloody wrong with "Wow, cool app you made".

I was interviewing for a new position that would be primarily Android development with a chance that I would help out on iOS when necessary. When I got their coding challenge, it had to be done for iOS in Swift. Made no sense, but now I can say I finally wrote a project in Swift.

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

When a hiring manager wants 5+ years experience in swift.
Swift release date = June 2, 2014.

GOD DAMN !@^@ react-native bridge to #@$^&ing objective-c bridge to an intermediate objective-c friendly #$@!ing swift class to communicate to a @$#!ing external swift framework #$@!ing POS!

And $!@# you Apple Mach-O Linker error!

Swift changes syntax again! Apple is treating their language like an Apple product. Why can't they decide? What's that? you have a project? Goodluck converting your code when we decide to change everything ;)

Unrealistic employer:
Looking for a Full Stack developer with 8 years experience in Swift and 10 years experience with PHP.

Deprecating '++' in Swift is a developers nightmare..

Not everyone can code, even those who are certified to say they can. True for school and work.

Anyone have one of the new MacBook Pros with Touchbar? I'm looking for some project ideas to work on.

I already am working on a project for the Pi-hole project (network wide ad-blocking) but I am looking for some other good ideas. I think Apple's view of the Touchbar fell short, but as developers I think it opens up a lot of possibilities to use it as a great information/monitoring tool.

I am also still learning Objective-C and Swift so I am a newbie.

Started learning Python from Java, C#, Objective-C, Swift.
It’s like Rocket Engineer who have to build a car. It’s easy but you have to learn almost everything from the beginning.

I never have touched Swift, not did I touch iOS.

A friend needed help making an iOS game in XCode for his work. I spent 3 hours of hell making his game from 0 knowledge.

Never again am I touching it again *shiver*

(Swift seemed pretty nice to type though..)

I hate how the IOS developer of our team gets all the recognition for an app we made just because the manager has a bloody iPhone, even though I did the entire backend and Android app.

When it’s 3am and you are working on an exception for more than 2 hours and have optimized your whole code just to be sure and remember you are writing swift not java: some ints have low max value like UInt8.

Started learning swift yesterday, and still want to write a semicolon after each line..

I love swift ;)

It's almost end of shift and I just want to get this React Native to run. Fuck!

When you have to sit with a developer and walk them through coding a solution step by step, but they have more experience than you in your field. I had to show them how to unit test the thing they wrote properly as well, because they couldn't figure out you need to actually call the method you are unit testing in your test.

(i love swift!!)?!there's nothing bad about it)!)?)!!

COBOL, Clipper, DBase, FlashCode, DOS 3.30, Novell, dot-Printers ... Now learning Swift... Emojis for variables! ... I'm to old for this..... Damn millennial languages.

Every FUCKING time iOS releases a version update, I have to update my Xcode, my code to the latest swift, my third party libraries..
Do you feel my pain , Apple?

Just developed my first interactive iPhone app using Swift!

It's only basic, changing the screen when tapped from black to white like a flashlight, but feels great to have done it after learning the language over the past few weeks. 😊

@bhargav-mogra This is Kotlin for you. In response to your rant about Swift ranges.

Updating a legacy written by the ceo from swift 1.2 to swift 3.1
No storyboard, main controller with 2200+ lines of code and viewDidLoad method with 500+ lines of code.
Almost no comments and code is illisible.
Weeeee

Had a swift 2.0 project with 32 warnings.
*updates project to Swift 3.0*
756 warnings. Can anyone beat me?

Side project is swift. Loads of feedback! I'm happy. Fucked up part is the users who wants it uses Android. Oh well, time to learn React Native

Hey everybody been a while but I have a rant. Swift fucking swift and IOS dev. Okay so been learning swift for some frontend casual work, no worries they are lending me a mac to work in.

Now comes the rant part IOS is fine to work in I dont have any qualms about platform but.. FOR THE LOVE OF COMMON FUCKING SENSE GET SOME FUCKING CONSISTENCY.

You have made swift statically typed language to supposedly make developing more consistant and better fine no worries i dont like static typed languages cause they are unnecessary but fine. then you go NAH FUCK IT EVERYTHING IN A MODULE IS IN GLOBAL SCOPE, FUCK IMPORT STATEMENTS, FUCK MAINTAINABILITY AND FUCK YOU FOR ASKING.

I was thinking maybe I could learn Swift. Then I saw the accepted pull request about deleting i++ and i-- operators...

Seriously wtf, i mean OK setting them as deprecated, but deleting ? Dude no

Swift 1 and 2 were really pain in the ass!! You had to write God damn completed word of each statement. Eg : "presentViewController" is now "present" in Swift 3. Or that fucking "NS" in every object :)))
Thanks God! Thanks Apple! No more bull shit keyword!

GOD ALMIGHTY I HATE SWIFT & XCODE...

Why the fuck does it take a horrendous amount of time to muck about with layout constraints. Why the heck does xcode choose to add constraint layouts to elements that already have pissing constraints! Why does dealing with something as trivial as tables have to be so god damn fucking involved when HTML and CSS let me create and style tables in fuck all lines.

And what the hell is up with how pissing long xcode takes just to figure out that 1 extra line of code I've just added. You jump to another file and xcode finally decides to be an ide again and bitch at the fact that you've forgotten to add some parameter or that they've decided to rename paramter "x" since version fuck nows what.

Working with abstract classes is fun, lets use protocols (because interfaces are too old school) and then lets tack on something we call extensions and then lets make people piss about with convenience initializers.

And lord almighty, what the fuck is up with casting, what all this ?! BS. What's wrong with just checking if the value is null in the first place, or whats wrong with giving something an initial value, oh because having to unwrap shit is more elegant right??

And good god, I need to own a fucking cinema screen just to have the storyboard open, there's less fucking panels on the Sistine Chapel ceiling
then there is in xcode.

Lately I needed to write some swift code and I‘ve never used it before. But acutually I find such a beautiful langange, maybe the one with the best type system ever.

Swift for the win!

I keep jumping between unfinished personal projects and then i get busy with the job, when I try to go back to them, I lose interest! Any advice?

Having to use Xcode 4 alongside the new 8 to support old iOS versions. I almost wrote the code twice, once in Swift and once in Obj-C.

Just saw a job ad asking 8+ years of Swift experience.

Swift is a language that appeared 4 years ago >:-(

About to start my first ever freelance job. The problem is I think I've overestimated myself and under quoted for the project.

Hoping for the best and I'm any case, this will be a good experience in terms of learning about the freelance world right?

I sexually identify as Objective-C

I actually would love to write everything in objective c
Even my node/react applications

Since I learned Swift I find myself missing it so bad when writing in other languages.

"Have you tried regenerating your provisioning profiles?" Say it one more time mothefucker I dare you I double fucking dare you.

New in my job
Start to work on a abandoned project for one of our client not very happy cause the lack of update
Go for a critical issue which exists since 2 months where everyone was telling me that they passed a huge time working on it with no answer
*check error*
*check code*
The code is so fucking much not DRY so I was able to see the same 4-5 incriminated lines elsewhere
*see that the request is lacking of one parameters just has the error suggests*
*copy paste the missing line*
*it works*

I’m now a hero for them but they become fucking peasants for me

(In addition, when code reviewing, some one had the nerve to tell me that “haha it was nothing much finally, it was easy”
To him : fuck you, eat my 💩)

It drives me Insane that AWS still doesn't support Swift 3 for iOS. We're almost to the point where Apple is going to drop Swift 2 support in XCode and Amazon STILL has not gotten it.

I've started deploying Gateway APIs in Objective-C and linking them to the bridging header just so we can finally move foreword in our company and quit relying on legacy Swift support. Which is something I was really trying to avoid because we don't like mixing languages unless absolutely necessary. It's not a problem, but it's incredibly annoying to me. What IS a problem is having to start new projects already using legacy code from the very beginning.

What is amazon going to do when the next release of XCode comes out? Tell all new customers to downgrade?

Why even offer native Swift APIs if you're going to go this long and still not migrate, Amazon?!

Gotta love Swift

When you get used to Swift and keep forgetting semicolons in other languages.

I've been writing Java the last few days. Really makes me remember why I enjoy writing objective c / swift so much. It's not necessarily the crazy syntax of objective c. It's the conventions behind the languages. It's very easy to make your code read like prose. Which when you become used to this it's very hard to jump back into spaghetti code with abbreviated variable names and such.

If you wanna think that I'm a bad programmer, that's ok, but I can't put up anymore with Xcode.

Jesus Christ. An entire afternoon spent trying to make an array with two dimensions. I tried every fucking way I found in SO, in the apple site and in every another site that I found in my way.

First: For every example for Swift 3 there's another 10 for Swift <3.

Second: Mutable arrays, as I'm noticing, aren't a thing anymore, so, to declaring array size we go! Except it's impossible to. Tried 3 different ways. Not a single one worked.

Third: Actually, one of the 3 tries worked, for int arrays, and for some obscure reason it won't work for strings, as declaring the array as [String] is too general for swift, I mean, I completely agree with it, a [String] array could contain anything right???? FUCK NO. IT CONTAINS STRINGS YOU FUCKER!!!!

I swear, if the equipment was mine and not from the office, I would have thrown that piece of shit which disconnects from the fucking computer every 30 seconds that apple calls keyboard out of the window already.

Why the fuck do I need to develop for iOS in swift/xcode?? There's so many cross platform alternatives out there, good ones in fact, but no, we must build the applications natively or else the phone will catch on fire according to my boss.

I kinda liked Apple until now.
From now on? Fuck Apple.

Awkward, but the only possible way.
Either I didnt figure it out or shame at Apple, this is not a good way to handle this.

Client from hell (if you've read my past rants) came back asking for information that he had provided me months ago.

I'm not your Google Mr client from hell, search it up yourself.

That's what I said, only in my mind though.

Unfortunately, I went to be his Google. Am I too kind? Should I just reply with a nicely worded "I don't know".

Me: Build Swift 3 Project got 1 warning: Conversion to swift 4 available. : “Let’s try that” after that archives it: 100 warnings and 20 errors -_-

Why can't the iOS documentation save a cookie to my machine so it can remember what fucking language I want to view it in.

How I always feel about Xcode when compiling Swift code, opening storyboard files, or just in general.

We need to make some of these stickers. ++

Having to deal with people's unrelated hatred like this...

Guys.... Were getting famous?
Oh shit that's Facebook....
* Posts the screenshot and runs away :) *
Taylor Swift...... You betrayed?

When Xcode 9.3 is available, but Swift.org hasn’t updated to Swift 4.1 yet.
What the hell? 🤦🏻‍♂️

Update:: just kidding, it shows apparently. Ugh.

Notice how the Apple code samples have moved from the very well designed Objective C to a mature Swift... (sorry, typo, manure Swift) Swift 1.0, wait 2.0, no hold on 3.0, oh yea 4.0. It's a moving target for their developers with code samples all over the place...

Once Swift stabilizes, sure, ok, force everyone and everything to change (seriously?).

Apple, why the FUCK do you think we want to deal with your beta crap forced down our throat? Its bad enough the language is an inconsistent illogical mess but having to come along with you for the 'we-don't-have-a-clue-what-we-are-doing' ride is utter bullshit. Leave the GOD DAMN Objective C samples up for crying out loud.

My life ends in a simple sentence:

"Unexpectedly found nil while unwrapping an optional value"

Only Swift developers will understand.

Converting swift 2 to swift 3 , started with 509 errors, down to 240.

Fuck this!!!!!!!

Some people really love the programming language they are using 🙊

Swift for Android can be real soon

Being a full stack developer has been an amazing journey. Looking at a project and understanding how the entire stack work starting from the mobile apps, APIs and DB is a total bless.

Nevertheless, lately switching context between modern languages has been extremely frustrating.

Swift looks like kotlin, elixir looks like ruby. Hell even swift and ruby are very similar.

Writing ruby in Xcode and wondering why the fuck Xcode complaining. Well no shit, swift is not ruby. Took me 5 mins of head scratching to notice it 😢

Hell I am now writing down the latest language I am working with on my hand to keep track 😂

Build Phase Scripts in Swift

Almost done with my app, major Firebase update and most of the code changed :-(

I'm loving language like Swift .... No semicolon (;)

What will you do when you find this on someones code ?

Finished writing code for a feature. Begins code analysis. "Analysing code" moments later "Build Failed". Really?! fucking really?! you tell me that now?

Ok granted it is nearly 1AM here I should go to bed. Good night guys!

Our Swift teacher at college manually creates a Podfile for every project and copies and pastes the basic initialization from an existing project, pastes the cocoapod dependencies and then installs them using terminal instead of just doing a pod init and then using nano or vim to paste the dependencies right inside the terminal. These are the times I genuinely feel sad for the way Indian education system is and the way we're taught coding in colleges here.

I don't know if our QA is good enough. We were developing an app for both ios and android. I, an ios developer, told the QA guy that it will take long before uploading the app in the testflight (convert swift2 to swift3). After a week the app is now uploaded in the test flight and at the same time my partner, an android developer, uploaded the android version of the app in the play store beta. The QA guy started to raise bug issues about the android version. He wanted to fix the bugs immediately since our boss needed to upload it in the play store and appstore. The QA guy kept on complaining to my partner why the android version is buggy. Then he said something we, me and my partner, facepalm.

The QA guy said " You shouldn't convert the app to swift 3. The ios version is fine when converted why the android version is buggy. You need to revert it back to swift 2"

We sit there in silence, thinking if we pity the QA guy or laugh at him.

Client wants me to do something even Google can't.

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

When you’re out of town for the night and you left your MacBook at home on your desk... what a genius I am.

IOS or Android Swift or Java/kotlin

I can't stand Swift's initializers. No other languages have the problem with constructors/initializers that Swift does. It's a complete failure of a feature and to hell with safety if it comes with this cost.

Just to illustrate how ridiculous it gets, I want to have a class where my initialization logic can be split among reusable parts. That is, the logic that initializes the class with no parameters has logic that I want to reuse in my other initializers. Simple DRY stuff. Well, the only way I can do that in Swift is if I use a convenience initializer that calls another one. But convenience initializers have completely different rules from designated initializers (again, something only Swift does).

For example, you can't access "self" until you call a designated initializer. You can't chain designated initializers, and if you want to chain anything in the same class you have to handcuff yourself by using a "convenience" initializer (there's nothing convenient about them, I might add).

So now I want to subclass my class and initialize myself using one of my superclass initializers. Oh but the one I want to call is a *convenience* initializer so I can't, unless I turn my new initializer into a convenience initializer. Except wait, a convenience initializer must delegate with self.init(), so it can't even call a superclass initializer!

And it just goes round and round and round. I don't know if I should try to convert all of my initializers to convenience initializers or the other way around.

Why all this nonsensical madness? Get rid of the distinction and go back to nice clean powerful initializers like Objective-C. I mean what does it have to take? This is a complete nightmare.

I can remember a day which I really close to crying why my code doesn't work! Then I remember that fucking line of code should be run async! :/

Is it me, or writing Swift after several JavaScript apps feels like writing "serious" code once again?

Swift SUCKS

Why?
Because of its absolutely useless complexity...
a total simple thing: i have a string and want to concat a integer with it, so:
var x = stringVar + intVar; right? NO
its var x = stringVar + String(intVar);
or getting the index of a element in a array?
var index = array.indexOf(element); thats logic, right??? Not for swift, gotta go with: var index = array.index(of: element); WTF??!!
And all the other shit: nil instead of null, int++? Nope.
And there are SO MANY MORE things, where u just think, Apple really though different........than all normal coding languages.......

I´ll honestly rather learn C and recode Ios or have a look at objective-c...

The awkward moment when you name your dictionary "dic" and realize that while explaining a piece of code to a female colleague. 😳

Many of you commented on my previous rant regarding my first ever freelance gig that I would definitely be back with even more to rant... here I am.

What was supposedly a 1 to 1.5 month long project became one that is stretching beyond 3, if lucky, else 4 months long. Requirements and scope evolving more complex and with variations more intense than pokemon evolutions.

I fucked up. I signed a contract that nobody would have. I didn't plan or protect my ass enough to prevent such shit from happening. I severely underestimated and hence under quoted. This is one of the nightmare situations a freelancer could be in (in my opinion). I mean it could only get better... Right? I'm preparing myself for one hell of a payment at the end of the project. Brace yourself, payment is hopefully coming as fast as the number of seasons it took for winter to come in GoT.

On the bright side, I'm currently working on a new project with a client that is indeed much much better than this first. I mean he is a nice person and communications thus far has been nothing short of great.

I guess it's good to start with your expectations rock bottom, that way nothing else can be worse, I hope.

Headache in instance initialisation Swift

Why the hell is the standard size of swift views 0. Who thought it would be a great thing not knowing why the view is not showing.

Finally installed iOS 10 Beta 1 on my iPad.
I will say this, Swift Playgrounds is a lot of fun!

Firebase or Self Developed Backend for mobile apps?. Which one to use if you have a fixed number of users.

So frustrating to learn Swift when I already know objective-c. It's like I know what I'm doing, but really, I don't

Ok so Swift's module system creates implicit namespace, meaning gone are the days of Objective-c frameworks / classes having prefixes.

I get that, and its a great advancement. But when I'm using 3 different social media SDK's, a networking library and some persistence cocoapods and I have to use classes called "AccessToken" and "Manager" ... come on guys, name your shit better.

I'm looking at you Facebook and AlamoFire!!!

Me coding in swift:

func doStuff() {

// code

}

"oh I see the code isn't working yet. Let me try this"

func doStuff() {

DispatchQueue.main.async {

// code

}
}

Looks familiar?
I really need to start giving more descriptive names when I test code..

Var that=
Vat thatt=
Var thattt=
....
Func workFFS=

Apple did a good job with Swift 👍🏼

I hate it when my language stop supporting '++' and '--' to make it easier to write. Like 'i++' is so harder to write than 'i +=1'

Did you know Swift can't handle generics over protocols (interfaces)? Me either until just now. 😣

I've already gave Go, Rust, and Kotlin a whack at to varies degrees of success. Now I want to try out the Swift programming language. But it's macOS and Linux only, and I'm stuck on Windows. I get it, Apple, you're not Mozilla, nor did you make the language an EMCA standard like Microsoft did for .NET/C#. Still, they're so close to having Swift not end up like Objective-C - not that it was a great begin with.

Credit for at least being open source, though.

So I just started learning Swift, and I think it's modern, beautiful and a bit weird. Like the Portuguese of programming languages.

I think it should be used more.

Situation: I'm a junior, working at company X since about the start of this year. We have a mixed team of native Android and native iOS developers. The architectural design decision was to build a separate iOS and a separate Android app.

Recently, during a problem solve session with other teams, other developers were complaining: why not use React Native, why not use Xamarin, why not use PhoneGap.

I'm so sick of this shit, if you have your users in mind, if you care about UX and UI and if you care about building an actually good app, GO NATIVE.

“Hey, did you know that the new Xcode never crashes again?”...

In the middle of the night, in my dreams...

Verbose is such an understatement for a python programmer to describe swift 🧐

Anyone else hope Google makes swift a first class language on android?

When droid devs try and code swift in a java style. FML

Swift is such a horrible language now that I am actually using it. You have protocols that don't behave like interfaces, classes that aren't objects, structs that aren't passed by reference. And stupid counterintuitive generic grammer. I feel scammed.

I can't take this Swift compile time anymore. It's up to 40 minutes now and all we can say is "optimize the code" and "get faster computers"

Is it just me, or is it the worst possible time to jump into coding for Apple products?

I remember trying to figure out Xcode a few years back and making some small bit of headway. More recently it seems that all the old tutorials in Objective-C are out-of-date, and half the Swift ones won't compile because of mutually incompatible versions...

So, I have my first ever on site interview on Monday for a Mobile Software Developer position.
I’m super excited but also super nervous.
You guys have any tips for not Richard Hendrix-ing the on site interview? 😂

is it the fact that I'm running XCode on a '11 MacBook Air or is auto complete just the slowest thing ever. I feel like it adds so much dev time

Why doesn't UITextView have a placeholder?