I know what my e-mail address says... but I have to say, the integration of AI with the code completion in Xcode Version 16.2 beta 2 (16C5013f) is so good it is scary. It is like it is reading my mind. I'm getting nervous about getting an MRI "Sir do you have any metal in your skull?" Me: "Oh god, did they implant some shit for Xcode to read my damn mind... this is going to friggin hurt!"

But seriously, I'm not at all a Swift fan but I have to say that with this AI auto complete, it is like having a "yea, this is how you normally would do this, how about we do this here" helper in the Mac.

But since the Xcode windows are all these dumb ass file browsers instead of document windows, I'm going to maintain: Xcode (still) Sucks... but a little less with this shit-hot AI code completion!

I can understand your point about xcode but what do you dislike about Swift?

@Lensflare It says "safe" but still crashes. It makes me jump through hoops in its "help" with managing memory "For me". My non-swift software doesn't crash b/c of any memory handling... even when the machine runs out of RAM.

Having the runtime engine to support Swift is grossly inefficient. Then top that off with Swift not supporting bit level operations beyond ANDing and ORing...gah

The Swift business of (_) is bizarre, along with the other use of special symbols that feels like ADA. I'm fluent in C, C++ Objective C, Pascal, ObjectPascal, FORTRAN, a half a dozen assembly languages and three machine languages (aka hex code). Swift tries to obscure the "Machine" and remove it from the language construct. That whole "optionals" and "unwrapping" thing it does which has no relationship to reality in the computer itself, drives me nuts. In my mind it is a failure in the model of "not having to deal with memory". They need to learn from MS BASIC circa 1980s