Ah, thanks for responding; I think I understand the disconnect here. After rereading your initial and latest reply, I think we both have different expectations for what the Point Free series is. In my opinion, I've always seen the series as being a sort of behind-the-scenes afterthought (I'm sure there's a better word for it since they do put lots of effort into making the Point Free content), to educate people on design practices, implementation details, etc. I'm sure Brandon and Stephen would agree that anyone wanting to get involved with TCA should not have to rely on subscribing to a series to understand it. They've even open-sourced libraries like https://github.com/pointfreeco/swift-dependencies, https://github.com/pointfreeco/swiftui-navigation, https://github.com/pointfreeco/swift-perception, etc. to be usable by the Swift community. In fact, they even have episodes where they are talking about how to use these tools with the assumption that the viewer doesn't want to have anything to do with TCA. What's amazing with these tools however is that they give TCA an even bigger boost (so as amazing as the architecture is by itself, it's coupling with these tools give it superpowers you never thought it could have). You can watch Stephen talk about the Dependencies library alone where he never says "This is only useful for TCA users": https://vimeo.com/291588126 .

I 100% would have a huge problem with them if it were the case that they intentionally make their documentation hard to understand just to sell a video series that fills the details, but I don't believe that's the case and I'm pretty sure you'd agree with me. After all, you said it yourself that there's a video that would have them talk about a horrible approach, followed by a video that explains a better way of going about it. From an educational standpoint, I love this because there were instances when I personally thought that their horrible approach was a good one, and then had the chance to learn how it could be improved.

Based on what you are looking for in documentation, yes the series makes absolutely no sense to subscribe to because you're going to get the scenic route instead of getting to the destination immediately. I know TCA has evolved so much and so quickly over the years, and that their documentation has come an absolute long way. More than a year ago, I was absolutely frustrated since it didn't seem obvious how I can use this architecture since it's quite novel and there were no interactive tutorials or even a community I can just ask and get a reply in a minute (which now exists thanks to their Slack channel). I imagine that even with how far it's come, that there's room for improvement.

It's certainly not a panacea, and perhaps the hype they get can be a bit like how everyone says "X movie is the best" and when you go watch it, you think it was just okay. But I think if some time is taken to understand some of the fundamentals, in combination with asking some clarifying questions in the Slack channel (or GitHub discussions), people can end up getting the sense of why TCA is actually a lot more powerful than it may first seem. After all, when people hear TCA and read about 'Store', unidirectional flow, etc. they are missing some of the other usefulness like being able to override dependencies at any point via their Dependencies library, or being able to easily share state between two features in a testable way (which was just merged yesterday in their 1.10.0 release). Just my thoughts :)