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

Swift release date = June 2, 2014

😂👍🖕

Swift 😐

People with programming languages named after them:

Haskell Curry
Ada Lovelace
Agner Erlang
Blaise Pascal
Taylor 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.

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 !

Tonight: Learning Swift while listening to Taylor Swift.

Poopy function in Swift

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

I think they are looking for time travelers..

My Chrome tabs everytime I try something with Swift.

IntelliJ sounds like Taylor Swift

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.

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

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 )

Kotlin: I don't have ternary operator, it's bad for readability
Swift: I removed ++ and --, cause they are old fashioned
Dart: *screams*

I love how my colleague impress me

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"

Shake it off , shake it off :v 😂 Taylor Swift

User removes admin access to himself and complains why he can't perform admin functions...

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)]

Hopefully it's written in Swift!

"if it compiles, it works"

Random thought: what would a Taylor Swift song about the Swift programming language sound like (besides catchy AF)?

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

❤️ Swift ❤️

for (i = 0; i < polygon.count; i++) {
// some print statement
} **

This highly advanced and futuristic piece of code made the Swift compiler eat 14+ GB of RAM while trying to syntax-highlight, before crashing my 8 GB-equipped Macbook.

** yeah, "C-style 'for' loopz syntaxx deprecated since Swift 3 blah blah". Let's reinvent an industry-standard for no goddam reason, because Swift is the FUTURE, oh, and because fuck you by the way.

Just realized that you can use emojis in Swift code 😮 #uselessbutinteresting

So in Swift days start counting from 1 and months start from 0. Because why not 🤷‍♂️

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

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...

Yup. I just built the calendar app in a Swift Playground.

My girlfriend started to develop iOS. After that she says Fucking Xcode and Fucking Swift a lot of times. I couldn't understand so I also tried to study iOS. And now I say. Fucking XCODE!!

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

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

Worst part about Swift 3, is searching on StackOverflow for the answer to a question but it's written in Swift 1 and it's not compatible

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?

<question>

Anyone excited to have Google possibly drop Java for Swift?

</question>

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

Yes I know that there is a promise lib for swift, fuck off

Explaining what a method does:
"""Python has docstrings"""
/** Java has javadocs */

SwiftHasSuperFreakinLongMethodNames()
Seriously Apple...

Learning Swift and a Timer as first Application. ;)

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

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

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

Leaving swift be like....

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

FML

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.

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

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

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

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

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

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

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

"/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

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.

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>)"

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?

why? just why???

Parsing JSON with Swift made me thank God for JavaScript.

❤️ Swift ❤️
A new minor version of the compiler has been released !
How sweet !
Which comes with the latest Xcode, which is of course mandatory to deploy on your devices !
How cool !
Let me also break all your code because I've decided to change some obscure programming paradigm, and also because FUCK YOU.

Short rant: I hate xcode, I hate Swift, I hate Apple.

After 3 weeks of intensive work (I'm an apprentice, part-student, part-worker), I was happy to go back to school and was like "Oh we're going to learn iOS, sounds cool !".

It is now friday, I have homicidal tendencies growing inside me, I want to cry whenever I hear xcode or swift.

Why in the hell I can't use a string argument when I'm calling a function NEEDING a string arg ?
Why do xcode take so long to tell me that there is a problem, why is the error message not explicit AT ALL ?
Why dictionaries so hard to manipulate, EVEN IN JAVA IT'S SIMPLIER.
Why putting our API call in specialized files make them run AFTER EVERYTHING ELSE and the solution that is given to us is deprecated since 5 years ?
Why is a classic c-style for loop is now deprecated ?

These are just a drop in the ocean of WHAT THE FUCK IS THAT that we came across this week.

Fuck Swift, fuck xcode.

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...

Being a swift developer while having a windows machine

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

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

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?

I FUCKING HATE SWIFT
THE SAME CODE DOESN'T COMPILE

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.

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 ;)

Having to write Swift and Kotlin for a while at work and now switching back to working on web technologies (for a different job), I would say JavaScript is ugly.

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 :)

❤️ Swift ❤️
Compiling fails due to many inter-dependent errors (think database deadlocks).
1 - Comment the code that produces the "locking" error.
=> Code compiles.
2 - Uncomment the code that produces the "locking" error.
=> Code compiles.

My peepee hard

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

❤️ Swift ❤️

"Module compiled with Swift 5.1.3 cannot be imported by the Swift 5.2.4 compiler"

but srsly

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!

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

When someone defines a Bool3 type in swift to represent true, false and undefined. Even tho swift already has Optionals as a first class feature. 😳

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.

I decided to learn Swift as I would like to make apps. So I installed swift and swift-jupyter in my Linux server after my 2012 iMac literally took 20 fucking minutes to compile `print("hello world")` in Playgrounds. Meanwhile, my server compiles python code in a swift jupyter notebook in seconds.

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

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

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

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.

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.

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.

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!

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

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.

Python + Javascript = Swift

Applied for a Android (java/kotlin) job and they gave me a swift code test 😕😕

In what fucking programming language a constructor can return a nullable value???

Swift of course. :|

Fuck apple :-)

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

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!

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.

I love swift ;)

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?

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.

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

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.

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

!rant
I’ve just looked into Rust a bit deeper and was absolutely stunned by how many things it has in common with Swift. The Syntax, the features, the concepts, the "philosophy".

Previously I thought that Kotlin is what comes closest to Swift.

Anyway, Rust seems like a beautiful language and it’s no wonder that it is one of the most loved languages out there!

The compile time index out of bounds errors blew my mind!

epic won against apple.
time to start learning swift

age += 1

( coz I'm used to using swift :3 )

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.

Swift for Android can be real soon

My life ends in a simple sentence:

"Unexpectedly found nil while unwrapping an optional value"

Only Swift developers will understand.

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.

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

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?!

The first time you forget semicolon in swift and you realize it doesn't matter

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

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.

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

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?

Is DevRant built on swift or objective-c...... thats the real question 🖥

Gotta love Swift

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

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...

Build Phase Scripts in Swift

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

Fuck this!!!!!!!

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

I'm a C++/Obj-C programmer finding it ludicrously hard to switch to Swift.

I find that the constant ability (leading to very poor programmer code) to reduce syntax and add tokens reduces readability and nowhere is this more apparent that with closures.

I'm working through (to my shame) Ray Wenderlich's Swift course and the closure chapter has this:

PS I loathe K&R as much as I do Swift so it's all in Allman formatting for clarity.

let multiply: (Int, Int) -> Int =
{
(a: Int, b: Int) -> Int in

// do Something else

return a * b
}
Why oh why isn't this more simply and elegantly written as:

let multiply = (a: Int, b: Int) -> Int
{
// do Something else

return a * b
}
The equals sign shows clearly that it's a closure definition assignment, as does the starting 'let'. But this way all of the stupid excesses, like the 'in' keyword, the repetition of the params / return type only this time with useful labels and additional tokens are removed and it looks and reads much more like a regular function and certainly a lot more clearly.

Now I know that with the stupid ability of Swift you can reduce all this down to return $0 * $1, but the point I'm making is that a) that's not as clear and more importantly b) if this closure does something more than just one line of code, then all that complicated stuff - hinted to by the comment '// do Something else' means you can't reduce it to stupid tokens.

So, when you have a clousure that has a lot of stuff going on and you can't reduce it to stupid minimalism, then why isn't is formatted and syntactically better like the suggestion above?

I've mentioned this on the Swift.org (and got banned for criticising Swift) but the suggestions they came up with were 'use type inference' to remove the first set of params / return type and token.

But that still means the param list and return type are NOT on the same line as the declaration and you still need the stupid 'in' keyword!

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. ++

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

In my latest installment of "Swift, WTF?", we look at the "if" conditional in terms of the Swift convention of:

if let x = y { /* ... */ }

so what this does :
1. declares x in the scope of the braced code
2. sets x to y (an ahem, "optional")
3. decides if x is not *nil*, then executes the braced code.

This is very similar in both the visual and the operation to the C code of:

if (int x = y) { /* ... */ }

1. declares x in the scope of the braced code
2. sets x to the value of y
3. if x is not zero, then executes the braced code

which is considered *exceptionally* poor style.

Neither the C nor the Swift construct result in a legitimate boolean value of "true" or "false", although C comes closer than Swift.

In the Swift case the *imaginary* "nil" value has to be interpreted as "false" and thus there must be extra code is for the conditional to check on whatever constitutes the **actual** value of nil in Swift and then set the condition to "false".

(remember boys and girls, "optionals" are not real, they are an imaginary language construct of Swift and have no legitimate counterpart in the CPU operations with memory and registers)

At least in the case of C, if the value of x is zero or NULL (which is 0) then it is technically a "false" which in C is 0. Regardless, it is really poor programming and anyone doing that on my team gets an ear full.

But in Swift this obfuscation of code is common and condoned! Well, why not put more of the program in the condition of the if? In fact, stuff the whole thing in there.. why not? 🙄

This just reenforces my opinion that Swift is not a bird but the stuff that comes out of the underside of the bird. 🐦💩

📋A hand-curated collection of useful and informative Swift Scripting materials.

The ++ and -- buttons here at DevRant do not work in swift at all. Damn!!

What do you think about swift ?..
It look like shit

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

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

Why iOS making it more complicated by releasing different syntax for every swift version.?
WTF

When engineers get so CS-driven they can’t see simple things 🙃

Another manager messaged me and my boss last night to ask whether he’ll have to expose a certain function to be available in objective c classes (we’re iOS devs and most of our code is in swift, but some older stuff is still in .m files). He said he dug into the lower level code and didn’t see any connections or exposures so he assumes he’ll have to add these. My boss concurred and told him to go ahead and make them available.

Then I showed up with my didn’t go to university brain & searched the codebase for calls to that function from .m classes. There were like a hundred lol, working just fine. It’s already exposed. Neither of them thought to do that.

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

Swift 5.9 will get huge additions to the language, compared to the current version 5.8, including type safe and checked macros much like in Rust.
And it’s still not going to be a major version bump to 6.0!
I’m thrilled to see what kind of stuff will be in 6.0 then! 😄

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.

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 -_-

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

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

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

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.

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.

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

Ladies and gentlemen, I am liking Swift and XCode.

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

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

Anyone ever tried Embedded Swift?

I should have posted this as a joke but, guess what Apple does NOT use when developing Embedded Swift stuff for their Secure Enclave firmware...

Yep, they don't use Xcode! 🤣🤣🤣🤣

(ok, I know, not surprising, but love the irony!)

Pointers in Swift.

Nuff said.

I'm not sure if need a doctor but i start liking swift

do {
liveLife();
} while (you != dead);

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".

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.

Apple did a good job with 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.

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.

IOS or Android Swift or Java/kotlin

I learnt Swift in 2016. 2017 has to be the year I turn Swift pro.
Happy new year to all and may your code come to life and thrive.

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 😂

!rant
Loving the the fact that constructors in Swift (initializers) can fail (returning null/nil) and be async.

In C# there is no other way than using static methods instead.

Company Hiring: We want 10 years of swift experience.

Me: ...

Swift: Created in 2014

!rant
Just tried Vapor (server side Swift) for a web api project and expected to be troubleshooting a lot but it was super easy and worked out of the box. Even openapi/swagger generation.
Now I‘m exited to build a fullstack project with native and web clients, completely in Swift. 😁

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"

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

}
}

Most funny part of swift, current version looks unstable and newer version is in hope.

Newer version has no regret of learning older version.

Common guys swift 3 is coming soon...

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

Swift: Have you ever noticed...

How many times the word "Safe" is used when describing Swift, yet there is no way to programmatically determine if a memory allocation failed?

How many ways this "Safe" system has a way of crashing:
1. Unwrapping a Nil Optional
2. Disconnected Outlets
3. Out-of-Range Array Access
4. Accessing Uninitialized Variables
5. EXC_BAD_ACCESS (Memory Access Errors)
6. Threading and Actor Isolation Issues
7. Type Casting Errors
8. Uncaught Language Exceptions
9. (fill in the blank?)

What frustrates me is that Swift lacks a language-level way to check if heap memory allocation succeeded. When you create an object like MyClass(), Swift assumes success—if allocation fails, the process dies instead of allowing your code to gracefully handle the failure.

And to avoid having pointers, it creates this horrendously random undocumenting syntax salad that is worse than ADA.

Swift, when you wanted a liter-bike and you get something else

Was working with Swift lately, we no longer have: x++ in Swift, and I wrote rowIndex += 1, and go-lint was not happy about it ....

Headache in instance initialisation Swift

Why are they deprecating ++ and -- in swift?? I love those guys 😞

Swift does some things really well, but then falls flat in others. Why is polymorphic JSON decoding/encoding such a pain?
In Kotlin, it's a breeze to support multiple object types.

Swift being too new a language to have proper unit tests so you have to bodge something together to keep the client happy.

Wow. Fuck converting code over to swift 3. Nothing automatic about it.

Is it just me or is objective-c syntax hideous after learning swift?

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.

Fuck you shitty clean swift architecture. I need to learn swift and mobile apps programming. As if that wasn't already hard enough I also need to understand clean swift. This shit feels like going in circles for the most basic stuff without any tangible benefits.

Checking Swift UI, first thoughts: goodbye Xcode freezing from storyboard loading ....

Sadly yes that's what I like about using Swift UI 😂😂😂

Oh and that binding, finally apple showed some love 😒

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

!rant
Learning iOS/Swift Programmer here.

I feel like Apple’s Developer Documentation is extremely hard to parse.
For one problem, it feels like there are 50 similar ways to deal with it; but only one way will actually work.

There also aren’t enough examples in the docs for me either, they just seem to go: “Here’s some code, figure out what it’s purpose is.” for most things.

I also feel stupid, because I’m using the Hacking with Swift tutorials to learn iOS Development(Great Tutorials Though); and I don’t know how to just build an app from scratch. (i.e. creating swift files and assets and compiling from the terminal.)

And using StackOverflow feels like cheating.

Lastly, I feel awful inside when other people see my work and think I’m a genius, when really, I feel like I barely know anything at all.

I’m I alone in this observation?
Or just dumb?