Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ #3138

Merged
merged 10 commits into from
Jun 4, 2024
Merged

FAQ #3138

Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 3 additions & 22 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -634,28 +634,8 @@ to a [Gist](https://gist.github.com)!

## FAQ

* How does the Composable Architecture compare to Elm, Redux, and others?
<details>
<summary>Expand to see answer</summary>
The Composable Architecture (TCA) is built on a foundation of ideas popularized by the Elm
Architecture (TEA) and Redux, but made to feel at home in the Swift language and on Apple's
platforms.

In some ways TCA is a little more opinionated than the other libraries. For example, Redux is
not prescriptive with how one executes side effects, but TCA requires all side effects to be
modeled in the `Effect` type and returned from the reducer.

In other ways TCA is a little more lax than the other libraries. For example, Elm controls what
kinds of effects can be created via the `Cmd` type, but TCA allows an escape hatch to any kind
of effect since `Effect` wraps around an async operation.

And then there are certain things that TCA prioritizes highly that are not points of focus for
Redux, Elm, or most other libraries. For example, composition is very important aspect of TCA,
which is the process of breaking down large features into smaller units that can be glued
together. This is accomplished with reducer builders and operators like `Scope`, and it aids in
handling complex features as well as modularization for a better-isolated code base and improved
compile times.
</details>
We have a [dedicated article][faq-article] for all of the most frequently asked questions and
comments people have concerning the library.

## Credits and thanks

Expand Down Expand Up @@ -711,6 +691,7 @@ This library is released under the MIT license. See [LICENSE](LICENSE) for detai
[gh-discussions]: https://github.com/pointfreeco/swift-composable-architecture/discussions
[swift-forum]: https://forums.swift.org/c/related-projects/swift-composable-architecture
[testing-article]: https://pointfreeco.github.io/swift-composable-architecture/main/documentation/composablearchitecture/testing
[faq-article]: https://pointfreeco.github.io/swift-composable-architecture/main/documentation/composablearchitecture/frequentlyaskedquestions
[dependencies-article]: https://pointfreeco.github.io/swift-composable-architecture/main/documentation/composablearchitecture/dependencymanagement
[getting-started-article]: https://pointfreeco.github.io/swift-composable-architecture/main/documentation/composablearchitecture/gettingstarted
[navigation-article]: https://pointfreeco.github.io/swift-composable-architecture/main/documentation/composablearchitecture/navigation
Expand Down
Loading