Twitter | Search | |
Steve Troughton-Smith Feb 11
Oh wow — you wanted a Catalyst halo app, well how about Swift Playgrounds? Congrats to all involved!
Reply Retweet Like
Steve Troughton-Smith
Think about this: Swift Playgrounds is how Apple is teaching kids to code. Swift Playgrounds on macOS only supports UIKit and other Catalyst-ready APIs. I'll let that speak for itself
Reply Retweet Like More
Roben Kleene Feb 11
Replying to @stroughtonsmith
I don't think there is any confusion about what Apple wants, the question is whether that's really the best choice.
Reply Retweet Like
hhas02 Feb 12
Honestly, we’re so far past the point of Wrong Choice now the only option is to keep on going. was classic tail-wagging dog; Apple needed a better Obj-C, and got a better C++ instead. Everything since then has been duct-taping over that chasm.
Reply Retweet Like
Tim Feb 11
Replying to @stroughtonsmith
SwiftUI works too Clearly Apple sees AppKit as the past. I think they see UIKit as the present and they’re trying to make SwiftUI the future. (It needs a hell of a lot of work, though. I’m interested to see what WWDC brings us!)
Reply Retweet Like
hhas02 Feb 12
Given the unpleasant impedance mismatch between ObjC (Smalltalk) and Swift (C++) worlds, a native GUI toolkit can’t arrive fast enough. Okay, it won’t be much of an improvement over everything we had a decade before, but at least [hopefully] it won’t be intentionally aggravating.
Reply Retweet Like
Anthony Feb 11
Replying to @stroughtonsmith
What a clear error message
Reply Retweet Like
hhas02 Feb 12
Replying to @stroughtonsmith
“Swift Playgrounds is how Apple is teaching kids to code.”
Reply Retweet Like