swift-composable-architecture VS swift-parsing

TCA for short. Very scalable, quite promising, quite popular. A decent alternative for MVVM enhanced by the Clean Architecture. You can learn more about it in a Point-Free tutorial and on GitHub.

🙏 Built with SwiftUI and The Composable Architecture (TCA): This isn’t a feature, but I just want to express my gratitude to the creators and maintainers of these two frameworks, which have played a huge part in making me fall in love with iOS development.

Razliciti alternativni frameworci i arhitekture - Recimo, na pamet mi padaju Composable Architecture (https://github.com/pointfreeco/swift-composable-architecture) i RIBs arhitektura (https://github.com/uber/RIBs). Ok, ove arhitekture resavaju neke probleme. Ali da li problemi koje te arhitekture resavaju solidan developer ne moze sam da resi bez vendor locka za kreatore tih arhitektura. Jesu one open-source, ali meni je rizik da se vezujem za bilo sta sto sutra moze da prestane da se odrzava.

I came across this post discussing MVM, MVVM, MVP, and composable architecture.

At a minimum, Composable Architecture, and now Dependencies from Point-Free.

I’ve built a couple of apps with this framework: https://github.com/pointfreeco/swift-composable-architecture

While there are apps that use a Redux-style architecture, the arch is still in its infancy in the community. There are a number of implementations each with their own take on Redux. TCA is probably the one with the most name recognition and documentation.

Learn it if the project at hand requires it. A lot of older, more mature apps will still use UIKit, so it’s likely if you plan to work an iOS developer job that you will need it. But it’s getting to the point where a lot of the forward thinking shops are already starting to integrate SwiftUI. (Me being one of them) which, btw, a lot of people will say SwiftUI isn’t quite there yet, and I mostly disagree. SwiftUI is good for a great many use cases. Yes, there are still pain points, but you can write most of the apps you’d need to write in SwiftUI. And there are great architectural frameworks out there that actually give SwiftUI an opinionated way to structure apps that is testable and maintainable. Check out pointfreeco’s The Composable Architecture (https://github.com/pointfreeco/swift-composable-architecture)

No idea about parsing and evaluating in the same library, but there’s an excellent parser library from PointFree.

Sorry about that, broken links have been fixed in the episode and here's a link to the library: https://github.com/pointfreeco/swift-parsing.

If you want to do parsing, I strongly recommend Point-Free's Parsing library!

Honestly I still have a difficult time understanding Regex’s, and maintaining them can be hard since once small change can completely change how the Regex works. I would instead opt for a real parsing library, like for instance PointFree’s swift-parsing, who’s clear and idiomatic API makes it easy to understand what’s really going on. It’s also very, very performant - almost as performant as making a custom hand-rolled parser.

Personally, I would pull out my parser library and use that (the documentation is lacking, so if you're just starting out it can be hard to figure out what's going on, but you could use Point Free's parser library to do it like so:

I’m currently using the composable architecture. TCA is the result of video series by Point Free that discusses what Apple provides with SwiftUI, in detail, and iterates though the of the evolution of the architecture, to fill in the gaps. Most of the content is available by subscription, but there is free content as well, which includes a four part overview on the architecture itself. I highly recommend subscribing as the detailed walkthrough of building the architecture is extremely useful and helps clarify some of the more complicated aspects of its use.