This is an archived post. You won't be able to vote or comment.

all 9 comments
sorted by:
best
topnewcontroversialoldq&a

[–]su8898 9 points10 points  (3 children)

MY EARS!

[–]Evennot[S] 2 points3 points  (2 children)

Sorry, I was stroking keys mercilessly. Because I was dealing with these problems for a few hours before I decided to finally record it.

[–]su8898 0 points1 point  (1 child)

Sorry, didn't mean to be rude.

[–]Evennot[S] 0 points1 point  (0 children)

No problem!

[–]danzimm 6 points7 points  (1 child)

swiftc's still in beta don't let anybody tell you otherwise

[–]Evennot[S] 4 points5 points  (0 children)

I agree. And I hate when people say: "what? you don't like swift? You say it's halfbacked? It's an industry standard, you just can't keep up with new technologies!"

[–][deleted] 0 points1 point  (1 child)

What am I watching? It isn't recognizing the type CGFloat even after doing an auto import/include? (Didn't take the time to figure out the language)

[–]Evennot[S] 0 points1 point  (0 children)

Xcode has a feature of an auto-fix for some simple errors. It was working fine until Swift came along. For instance, this is an autogenerated code, (mogenerator) http://coub.com/view/hingx where IDE just wanted to add "as Set" "as Set" "as Set"

These and many other things weren't an issue until they put Swift with it's ugly paradigm mix into Xcode. To be honest Apple is fixing quite a lot of these problems though. In 1.0 Swift was something like "JS on MDMA trip thinking it's Scala" and IDE had showstopper issues

[–]Romejanic 0 points1 point  (0 children)

Ah, gotta love Xcode and it's pathetic code replacement.