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

added FAQ item diff between cats and scalaz #1901

Merged
merged 14 commits into from
Sep 14, 2017
Prev Previous commit
Next Next commit
typo
  • Loading branch information
kailuowang committed Sep 7, 2017
commit ae0ca8482e6e8d8e63579e3c3374f70a30278ac3
6 changes: 3 additions & 3 deletions docs/src/main/tut/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,11 +26,11 @@ position: 4

## <a id="diff-scalaz" href="#diff-scalaz"></a>What is the difference between cats and scalaz?

The goal for both cats and scalaz are the same: facilitate pure functional programming in scala applications; the underlying core strategy is different. Scalaz took the approach of trying to provide a single batteries-included *standard library* for FP that powers the scala applications. Cats, on the other hand, aims to help build an [ecosystem](https://typelevel.org/cats/#ecosystem) of pure FP libraries by providing a solid and stable foundation. These libaries can have their own styles and personalities, competing with each other, while at the same time playing nice. It is through this ecosystem of FP libraries (cats included), scala applications can be powered with "FP awesome-ness" and beyond by picking whatever best fit their needs.
The goal for both Cats and [Scalaz](https://github.com/scalaz/scalaz) are the same: facilitate pure functional programming in Scala applications; the underlying core strategy is different. Scalaz took the approach of trying to provide a single batteries-included *standard library* for FP that powers the Scala applications. Cats, on the other hand, aims to help build an [ecosystem](https://typelevel.org/cats/#ecosystem) of pure FP libraries by providing a solid and stable foundation. These libaries can have their own styles and personalities, competing with each other, while at the same time playing nice. It is through this ecosystem of FP libraries (cats included) that Scala applications can be powered with "FP awesome-ness" and beyond by picking whatever best fit their needs.

Based on this core strategy, cats took a [modular](https://typelevel.org/cats/#modularity) approach and focuses on providing core, binary compatible, [approable](https://typelevel.org/cats/#approachability) and [efficient](https://typelevel.org/cats/#efficiency) abstractions. It also takes great effort in providing a welcoming and supportive [community environment](https://gitter.im/typelevel/cats) and a comprehensive beginner-friendly [documentation](https://typelevel.org/cats/#documentation).
Based on this core strategy, Cats took a [modular](https://typelevel.org/cats/#modularity) approach and focuses on providing core, binary compatible, [approable](https://typelevel.org/cats/#approachability) and [efficient](https://typelevel.org/cats/#efficiency) abstractions. It also takes great effort in providing a welcoming and supportive [community environment](https://gitter.im/typelevel/cats) and a comprehensive beginner-friendly [documentation](https://typelevel.org/cats/#documentation).

We believe that both cats and scalaz strategies have its merits and shortcomings, and it's a positive thing for the scala community to have both.
We believe that both Cats and Scalaz strategies have its merits and shortcomings, and it's a positive thing for the scala community to have both.

## <a id="what-imports" href="#what-imports"></a>What imports do I need?

Expand Down