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

polishing FAQ #1912

Closed
wants to merge 4 commits into from
Closed

polishing FAQ #1912

wants to merge 4 commits into from

Conversation

kailuowang
Copy link
Contributor

based on feedbacks from @edmundnoble on #1901

@codecov-io
Copy link

codecov-io commented Sep 14, 2017

Codecov Report

Merging #1912 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1912   +/-   ##
=======================================
  Coverage   95.54%   95.54%           
=======================================
  Files         248      248           
  Lines        4420     4420           
  Branches      121      124    +3     
=======================================
  Hits         4223     4223           
  Misses        197      197

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7c74048...6847885. Read the comment docs.

@@ -38,9 +38,9 @@ This should be all that you need, but if you'd like to learn more about the deta

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

Cats and [Scalaz](https://github.com/scalaz/scalaz) have the same goal: 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](/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.
Cats and [Scalaz](https://github.com/scalaz/scalaz) have the same goal: to facilitate pure functional programming in Scala applications. However, 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](/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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/libaries/libraries

@LukaJCB
Copy link
Member

LukaJCB commented Sep 14, 2017

I think the title in the FAQ listing is missing a question mark :)

@kailuowang
Copy link
Contributor Author

closing this since the changes were rolled into #1915

@kailuowang kailuowang closed this Sep 15, 2017
@kailuowang kailuowang deleted the polish-faq branch September 15, 2017 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants