Point-Free

We compare SwiftData’s new features with SQLiteData, starting with a domain modeling exercise. We will rewrite the Trips @‌Model classes into simple @‌Table structs, and we will explore how the Draft type can power a single form for both creating and updating trips: www.pointfree.co/episodes/ep3...

Introducing: CompilationTesting! Test code that should produce Swift errors, warnings, fix-its, and notes. www.pointfree.co/blog/posts/2...

Our “Designing for Isolation” series is now done, and in it we show the powers of separating the nonisolated bits of feature code from the isolated bits. 👉 www.pointfree.co/collections/...

This week we conclude our series by showing how to share isolation across boundaries! By abstracting our nonisolated core with a protocol, isolated shells can scope down to subfeatures while retaining all the benefits of controlled isolation. www.pointfree.co/episodes/ep3...

Come learn how to accomplish the seemingly impossible with Swift macros: • Customize macro logic based on static type information • Access static type information from inferred types Both things you cannot typically do by looking purely at the syntax! 🤯

@pointfree.co's series on advanced macro techniques wraps up with part 2: type inference. A great read for Swift macro authors. Check it out at www.pointfree.co/blog/posts/2...

This week we started reaping the benefits of "nonisolated core, isolated shell". We write features a single time, without thinking about isolation, then wrap the feature in the isolation we need. @‌MainActor for SwiftUI, arbitrary actor for tests! www.pointfree.co/collections/...

Learn about what went into designing its concurrency system in our latest video series: www.pointfree.co/episodes/ep3...

The feedback on ComposableArchitecture 2.0 has been pretty reassuring 😁

Advanced Swift macro technique: Accessing inferred types Macros only see the syntax of Swift code, so it seems impossible to access inferred types. But with a clever trick involving associated type inference, we can achieve the seemingly impossible! www.pointfree.co/blog/posts/2...

Which error would you prefer to diagnose? The one that is presented on the problematic line, or the one hidden in the guts of expanded macro code?

Part 1 of our Advanced Swift Macros series is out! You may think macros can only see the stringy syntax of Swift code, but it is possible to tease out some static type information. You can even detect if a type conforms to a protocol! 🤯 www.pointfree.co/blog/posts/2...

Come for the real world explanations of isolation in Swift, stay for the deep dives into esoteric underscored attributes like '@_inheritActorContext(always)' 🤣 www.pointfree.co/collections/...

We've got a new series of blog posts coming up: Advanced techniques in Swift macros We will show off a few clever tricks for teasing static type information in macros, something that is commonly thought to be impossible! www.pointfree.co/blog/posts/2...

Modern concurrency tools like nonisolated(nonsending) and Task.immediate got us closer to our goal, but not all the way. So we’re trying a new approach inspired by Gary Bernhardt’s “functional core, imperative shell”: Nonisolated core, isolated shell. www.pointfree.co/episodes/ep3...

We tried using two modern Swift concurrency tools to allow us to embrace non-sendability: • nonisolated(nonsending) • Task.immediate They got us close to our goals, but sadly there were still data races. Watch this week's episode to understand why: www.pointfree.co/episodes/ep3...

Our deep dive into Swift isolation from a few months back may have been a bit abstract for people, so we are bringing things down to earth by designing real world code with isolation in mind from the beginning: www.pointfree.co/collections/...

Our code is at an impasse: we want to embrace non-sendability, but async work seems to force us into Sendable. We’ll revisit our approach to this problem from ComposableArchitecture 1.0, see why it's not ideal, and search for a better way. www.pointfree.co/episodes/ep3...

We’ve started a new series: Designing for Isolation Learn how designing for isolation from the beginning lets you embrace non-Sendable types, maintain thread safety, and keep asynchrony from infecting every corner of your codebase. Follow along here: www.pointfree.co/collections/...

It’s time to put what we’ve learned about isolation into practice. We’re building the reimagined Composable Architecture 'Store' from scratch and exploring the benefits of strictly controlling isolation through every layer of the library. www.pointfree.co/episodes/ep3...

Earlier this week we held our first Point-Free Office Hour. We answered questions from our viewers and gave a tiny preview of a new library we are working on. Check it out: www.pointfree.co/office-hours...

Our first ever office hours for Point-Free Max members is starting now! www.pointfree.co/office-hours

It's our tiniest library ever, and it solves the last remaining problem with the @State macro, in our opinion. Use @LazyState to allow for dynamic initialization of state in your views: www.pointfree.co/blog/posts/2...

For the past 10 weeks we have analyzed many of the new SwiftUI and SwiftData features announced at WWDC26. We uncovered a lot of things that haven't gotten widespread attention in the community, and now the whole series is free! 👉 www.pointfree.co/blog/posts/2...

Last month we shipped 40 releases across 16 of our open source libraries, including new JSON and DB collation tools, preview traits in Dependencies, and the completion of a years-long package rename. Here’s a recap of everything that happened. www.pointfree.co/blog/posts/2...

We wrapped up our Swift isolation series a few weeks back, but our members have had some nice things to share since then... 😊 www.pointfree.co/collections/...

Compare to SwiftUI’s LazyState (wrapped in a macro by us), where we get to drop all the Optional dancing, potentially buggy “onAppear” logic, and generally write things as succinctly as possible:

Xcode 27 beta 6 quietly changed how SwiftData's sectioning APIs work. Did you notice? The @Query macro must now explicitly use the SectionedResults type, which means it is no longer possible to dynamically add/remove sectioning from a view.

There was an unexpected hubbub last week when we said lazy @‌State only works for private variables. Well, we're back at it. We feel @‌State still doesn't adequately solve the problem of dynamically initialized state, so we are introducing @‌LazyState: www.pointfree.co/blog/posts/2...

We explore the problems not solved by the new @‌State macro and explain why we think they should be solved. To close this gap we introduce a new @‌LazyState macro, which allows you to delay initialization of your state, all without introducing any new API! 👉 www.pointfree.co/episodes/ep3...

You've probably heard by now that SwiftUI has a fancy @‌State macro that lazily creates state, fixing a longstanding issue in the framework. But what you may not know is that the laziness only kicks in for **private** state. Get all the details here: www.pointfree.co/episodes/ep3...

The new @‌State macro uses a type called LazyState under the hood, and this type has secretly existed in SwiftUI for years! We lift the veil on this type in this week's episode to see how Apple was able to back port @‌State to iOS 17: www.pointfree.co/episodes/ep3...

The new @‌State macro fixes a long-standing bug in SwiftUI, that of objects being needlessly allocated. But have you looked at the expanded macro code yet? Looks like gobbledygook! We show that all of this code is essentially just 3 lines of code: 👉 www.pointfree.co/episodes/ep3...

I am quite pleased to see @pointfree.co doing proposal after proposal

WWDC26 brought the new @‌State macro to succeed the property wrapper, but what’s different about the macro, and how does it work? We’ll pick apart the cryptic macro expansions to see something quite simple at its core. www.pointfree.co/episodes/ep3...

Many took SwiftData queries being limited to SwiftUI views as proof that everything belonged in views. But appleOS 27 now allows queries to live outside views, which is something SQLiteData has supported since day one and back-deploys to iOS 16! www.pointfree.co/episodes/ep3...

We always felt SwiftData queries were needlessly constrained by having to live directly in views. That’s why SQLiteData was built from day one to work equally well in SwiftUI views, @‌Observable models, and even UIKit view controllers. www.pointfree.co/episodes/ep3...

This week we build a geofence editor using SQLiteData’s type-safe JSON APIs, and we show how everything is 100%, exhaustively testable. www.pointfree.co/episodes/ep3...

Announcing: Episode Search! This was probably our most requested feature. Have you ever wanted to revisit a topic but forgot which episode discussed it? You can now search our entire catalog of video transcripts, from speech to code. Try it out today: www.pointfree.co/blog/posts/2...

GitHub is having a rough day today, and luckily just last week we made it possible to log into your Point-Free account without GitHub! www.pointfree.co/blog/posts/2...

This year SwiftData introduced a brand new way to observe changes outside of the view where @‌Query cannot be used. What’s SQLiteData have to say about that? To explore, we’ll build a moderately complex geofence map editor and get full test coverage of the feature. www.pointfree.co/episodes/ep3...