A thorough article on TCA. Well done.

But that said, I have to disagree on TCA's suitability for use with SwiftUI. Redux-style architectures are traditional a poor fit for use with SwiftUI, which prefers distributed state bound as low in the view tree as possible in order to minimize view updates per action.

It's true that TCA provides some level of support to counteract this... but you have to understand and implement those solutions and they're not easy to understand.

SwiftUI is extremely opinionated about state, the environment, declarative views, bindings, and so on,

SwiftUI has a fairly well-understood update mechanism. Change the state, and the dependent view updates. Hundreds, if not thousands of articles and lessons and videos explain this... but TCA wants you to supplant those mechanisms with its own.

In short, it fights against SwiftUI's view of the world. And it fights against Apple's view of SwiftUI.

Finally, and as mentioned, it has a fairly significant learning curve. I liken it to a UIKit developer jumping in and trying to build a fully reactive program using RxSwift. You can do it, but first you have to learn about publishers and observers and event streams and maps and flatMaps and... I mean, you can do it, but it increases the cognitive load significantly.

Again, a well-written article that I enjoyed reading... even if I disagree with the premise.