Issue 222
Jun 04, 2024

Should you use Swift Package Manager as your default solution for managing dependencies? Or is it still worth using CocoaPods or Carthage? I'm sharing my opinion together with a detailed explanation of how to generate and publish new packages.

Developers and businesses are asking this question daily, so we put together an expert panel to settle the debate. Watch it here.

Even though you’re using a Button element, it doesn’t mean you’re doing it right.

WWDC is around the corner. What better way to prepare is by completing this quiz? Be prepared; those questions are not easy!

This article explains why I’m a big fan of defining @State properties private.

Did you know 0.1 + 0.2 could result in 0.30000000000000004 if you’ve used the wrong numeric type?

When you think about declarative APIs, you’ll likely think about SwiftUI. However, as explained in this article, you can also define declarative APIs for non-UI code.

This week's question is:

June 2nd, 2014, Swift got announced at WWDC 2014. I was lucky enough to be there in person, just as surprised as all other developers around me.

Nobody expected such a big announcement, and I can’t even remember rumors circulating that would hint at a new language.

Celebrating Swift’s 10th anniversary, I’d love to bring you back to my first Swift project experience. Right after WWDC 2024, I started a new project at the digital agency I was working at. We decided to go full-in on Swift to prevent the project from becoming a legacy from the start.

Today’s version of Swift is far from what it was in version 1.1. Of course, we had no async/await, and we also didn’t even have Codable! Can you imagine?

Projects would compile fine at first, but without incremental building support, my project became incredibly slow. I ended up writing code for an hour, hoping that one build after would succeed. Painful.

Stories like these allow us to appreciate today’s state. With WWDC around the corner and the release of Swift 6 coming closer, I’ve never been so excited to be developing with Swift.

Want to have your question answered next week? Ask your question on LinkedIn or Twitter.