I've been learning Swift lately, and I have to say I've *really* come to enjoy it. Sure, it has it's problems, but I feel like you always can find a solution to them, and I just really appreciate the sheer pragmatism.
Also: result builders are my favorite way to define UIs that I've ever used. It *actually* feels like a programming language that takes UI programming seriously and is willing to prioritize making UI programming ergonomic!
I’m using Embedded Swift to reverse engineer Disney MagicBand+
I'm making a seasonal anime guide app, in the open for all to experience and learn from.
Another short stream, but let's get those hashed emails compiling 😅
#Jiiiii #DevStream #tvOS #visionOS #macOS #iOS #iPadOS #Anime #SwiftLang #SwiftUI #Vapor #WebAuthn #BuildInPublic #TestFlight #PWA #WebPush
Come chill with me: https://youtube.com/live/VgTuxJt4-jw

Yay, "(at)c (at)implementation" is functionally equivalent to "(at)_cdecl()" and works on older macOS platforms. Compiled on macOS Tahoe with Swift 6.3, binary runs fine on macOS Sequoia.
(if only I could use @ without turning into an account link...)
So why would `AnyTransition.opacity` be marked as `unsafe`?
https://developer.apple.com/documentation/swiftui/anytransition/opacity
I'm making a seasonal anime guide app, in the open for all to experience and learn from.
Short stream today as the kiddo is having a lot of trouble sleeping, but let's make progress implementing out a type for hashed Emails!
#Jiiiii #DevStream #tvOS #visionOS #macOS #iOS #iPadOS #Anime #SwiftLang #SwiftUI #Vapor #WebAuthn #BuildInPublic #TestFlight #PWA #WebPush
Come chill with me: https://youtube.com/live/zwnt88PSRq0

RE: https://mastodon.social/@swiftlang/116286524514684047
With the new "(at)c (at)implementation" in Swift 6.3 does that mean I shouldn't be using the unofficial "(at)_cdecl()"? And will building it with Swift 6.3 work on older systems? Guess I have some testing to do.