Post

I just realized today it's been almost two years since I started the refactor of CiderKit to support #swift 6 Strict Concurrency. As for many personal side projects, I work on it when I can. However, in the meantime, we shipped Battlestar Galactica, which took a lot of my energy along the way.

24/10/26, 3:45 pm0 reposts1 like

Christophe Sauveur

@chsxf.dev

In order to learn some aspects of concurrency and actor isolation, I also worked on CiderKit.Tween. In retrospect, I had to take a step back on CiderKit's main project, but it was worth the time. github.com/chsxf/CiderK...

github.comGitHub - chsxf/CiderKit.Tween: A pure Swift tweening library that complies with Swift 6 Strict ConcurrencyA pure Swift tweening library that complies with Swift 6 Strict Concurrency - chsxf/CiderKit.Tween

Christophe Sauveur

@chsxf.dev

In 2025, "Practical Swift Concurrency" from @donnywals.bsky.social was also an important resource in my journey to understand it. practicalswiftconcurrency.com

practicalswiftconcurrency.comPractical Swift Concurrency - Donny WalsLearn everything you need to know to make optimal use of Swift Concurrency in your applications. This book covers everything from awaiting asynchronous method calls to building your own highly concurr...

Christophe Sauveur

@chsxf.dev

This refactor is not finished, or even perfect in its current state. But it is mostly done. No, I won't use a LLM. I want to learn and craft things myself. #noAI github.com/chsxf/CiderKit

github.comGitHub - chsxf/CiderKit: SpriteKit-based game engine, written in Swift, and provided with custom authoring toolsSpriteKit-based game engine, written in Swift, and provided with custom authoring tools - chsxf/CiderKit