Paul Haddad 1d ago
ObjC is so hard to read!!! Meanwhile…
Show threadPaul Haddad 
Nope, no issues here.
Apr 5 at 8:56pmWeb
Show threadPaul Haddad 1d ago
I'm stuck in Swift land for at least the next week, so expect a lot of moaning and groaning. There's for sure some parts that I like about it, if they had a version with maybe 1/4 of the features (i.e. needless complexity) I might actually say I'd enjoy using it.
Show threadPaul Haddad 1d ago
Oh and bring back F*****' header files you crazy bastards!
Show threadKuba Suder • @mackuba.eu on 🦋1d ago
@paul … but that was the worst part 🫣
Show threadJason Cox1d ago
@paul Oh gods no! 😱
Show threadErik Ableson22h ago
@paul Hmm, I'd like to see dynamic, read only header files that are automatically generated from the main file so I can use them to skim the interfaces and generate errors when my code makes no sense
Show threadPaul Haddad 1h ago
Yesterday's Swift week highlight was spending at least an hour trying to find the right annotations to tell the compiler/concurrency stuff what a couple methods do threading wise. Turns out I had the right combo from the get go but it’s broken in both Xcode 26.2/4 and fixed in the .5 beta. Couldn't tell in older Xcodes because Apple blocks old Xcodes from running in current OSes for "reasons”.
Show threadPaul Haddad 1h ago
Swift's concurrency approach is emblematic of its complete lack of pragmatism. Runtime sees hey I think this code is running in the wrong thread (or context if you must) what do I do? Warn and ignore, because it's probably OK 99% of the time, nope. Warn and correct, because you have enough info to infer what is probably needed, nope. How about crash 100% of the time, yep, that's the one.
Show threadSteve Tibbett1h ago
@paul There are domains where you probably want that (kernel stuff, secure code) and domains where leniency would be better. But Swift is everywhere.
Show threadPaul Haddad 1h ago
@stevex 100% and even times where you want it (debugging) and times when you don't (AppStore).
Show threadDominic Nieto1d ago
@paul wait Ivory is Obj-C?
Show threadErik Ableson1d ago
@paul Out of curiosity, how much if this is Swift's fault and how much the libraries?
Show threadJosh Hrach21h ago
@paul I've stayed on Swift 5 and been happy. The day I'm forced onto Swift 6 I'm sure I'll complain.
Show threadBruce20h ago

@paul « a version with maybe 1/4 of the features (i.e. needless complexity) »

That'd be Dart (what is used for Flutter).