What You Need to Know About #WWDC24 | Recap for Developers | @SwiftBird

WWDC 2024 is here, and it brings a lot of updates to both consumers and—most importantly—developers. In this video, I highlight WWDC24’s key announcements, including Swift 6, Xcode 16, Swift Testing, Apple Intelligence (predictive code completion and Swift Assist), and much more.

You can support the Swift Bird by…

Links:

Chapters:
• 0:00 Intro
• 0:50 Key Highlights
• 1:57 Swift 6
• 4:32 Apple Intelligence
• 7:06 Xcode 16 with AI Tools
• 8:48 Swift Testing
• 11:27 Updates in Other Frameworks
• 13:19 Swift on Server & Embedded Swift
• 14:39 Summary
• 15:45 Outro

The Swift Bird, a Yakov Manshin production 🎞️

Music:
• Beauty Flow by Kevin MacLeod (CC-BY 4.0)

#WWDC #Swift #softwareengineering

[bort]

Just found your channel it’s great! Any tips for someone trying to learn swift who’s new to programming?

[smotch]

awesome vid...btw 5:50 was there a new air released a few months ago that i missed?

[maila]

Thanks for being so concise, I love it!

[Vigotskij]

I was waiting for your review! Keep the good analysis and thank you!

[twenty-fifth]

I mostly took a break from Swift to pick up D because I wanted to get over my fear of C/C++ languages. Regular {} and ; were kind of hard for me to get used too.

But now I am back and I am super excited for Swift 6! I have been using since 5.9 and it is my go to 'feel good' language next to perhaps Nim or Crystal. I too and looking forward to the new testing framework.

My favorite new feature is the do catch error handling. I am working on a fantasy console, partly to build my own platform, partly to learn emulators and boot environments and partly because I love games. I think I can use that in managing console errors and validating contracts. I personally prefer to write code with explicit errors, so this is kind of my dream feature. I always liked how safe swift, it is almost like a less hair pully rust or a opinionated nim imho.

[JoãoSerra-zd]

Is it just me or these new testing examples and its way to write feels like more of a proxy of the code that is being tested?
I mean if we are testing a multiply for 2... the code is probably in the app main code not on the test itself since its the main code we are testing...
Not sure if I explain well what I mean. I'm sure I'll understand it better when I tried it later and find different examples to make sense of it.
But if the @test states a sequence of expected events/results... isn't that all what we expect from tests? the whole test? so why have the body of the test?

[DominikButz]

A new UI Framework and new programming language every year? Why should this be necessary or desirable? Can you elaborate? SwiftUI took years to become anything close to a production-ready framework. And why should Apple introduce a new programming language?