added FAQ item diff between cats and scalaz #1901

kailuowang · 2017-09-08T14:40:19Z

No description provided.

@alexandru

With @alexandru's consent, I adapted some content of a reddit comment of his to this item.

ceedubs

Thanks @kailuowang! In general this looks good. I just had a couple of minor thoughts.

ceedubs · 2017-09-08T16:13:03Z

docs/src/main/tut/faq.md

+
+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](/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](/cats/#modularity) approach and focuses on providing core, [binary compatible](/cats/#a-namebinary-compatibility-and-versioning), [approachable](/cats/#approachability) and [efficient](/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](/cats/#documentation). 


When discussing the supportive community, I think that it might make sense to point out that the community is governed by the code of conduct, as this is another difference from scalaz.

ceedubs · 2017-09-08T16:18:07Z

docs/src/main/tut/faq.md

@@ -8,7 +8,7 @@ position: 4
 # Frequently Asked Questions

 ## Questions
-
+ * [What is the difference between cats and scalaz](#diff-scalaz) 


Maybe this shouldn't be the first item in the list. I think that a lot of people come to Cats without familiarity with Scalaz, so something like "What imports do I need" would probably be a more straightforward first item for them than introducing another FP library.

codecov-io · 2017-09-08T16:40:16Z

Codecov Report

Merging #1901 into master will increase coverage by 0.24%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1901      +/-   ##
==========================================
+ Coverage    95.2%   95.44%   +0.24%     
==========================================
  Files         248      250       +2     
  Lines        4379     4570     +191     
  Branches      125      125              
==========================================
+ Hits         4169     4362     +193     
+ Misses        210      208       -2

Impacted Files	Coverage Δ
core/src/main/scala/cats/data/IndexedStateT.scala	`100% <0%> (ø)`
...in/scala/cats/data/IndexedReaderWriterStateT.scala	`100% <0%> (ø)`
...rc/main/scala/cats/laws/discipline/Arbitrary.scala	`92.75% <0%> (+0.69%)`	⬆️
core/src/main/scala/cats/data/package.scala	`88.88% <0%> (+3.17%)`	⬆️
core/src/main/scala/cats/syntax/monoid.scala	`100% <0%> (+100%)`	⬆️

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 d20af7a...c2a1e27. Read the comment docs.

kailuowang · 2017-09-08T16:47:26Z

Thanks @ceedubs , all valid points, addressed.

LukaJCB · 2017-09-08T17:23:49Z

docs/src/main/tut/faq.md

@@ -36,6 +36,15 @@ import cats.implicits._

 This should be all that you need, but if you'd like to learn more about the details of imports than you can check out the [import guide](typeclasses/imports.html).

+## <a id="diff-scalaz" href="#diff-scalaz"></a>What is the difference between Cats and Scalaz? 
+
+Cats and [Scalaz](https://github.com/scalaz/scalaz) has 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 have the same goal

longcao · 2017-09-08T18:22:13Z

docs/src/main/tut/faq.md

+Based on this core strategy, Cats took a [modular](/cats/#modularity) approach and focuses on providing core, [binary compatible](/cats/#a-namebinary-compatibility-and-versioning), [approachable](/cats/#approachability) and [efficient](/cats/#efficiency) abstractions. It provides a welcoming and supportive environment for the [user community](https://gitter.im/typelevel/cats) governed 
+by the [typelevel code of conduct](https://typelevel.org/conduct). It also takes great effort in supplying a comprehensive and beginner-friendly [documentation](/cats/#documentation). 
+
+We believe that both Cats and Scalaz strategies have their merits and shortcomings, and it's a positive thing for the scala community to have both.                           


I saw this in gitter - I think it could either be:

We believe that the Cats and Scalaz strategies have their own merits and shortcomings, and it's a positive thing for the Scala community to have both.

or

We believe that Cats' and Scalaz' strategies have their own merits and shortcomings, and it's a positive thing for the Scala community to have both.

johnynek · 2017-09-14T17:04:10Z

👍

edmundnoble · 2017-09-14T17:16:26Z

docs/src/main/tut/faq.md

@@ -36,6 +36,14 @@ import cats.implicits._

 This should be all that you need, but if you'd like to learn more about the details of imports than you can check out the [import guide](typeclasses/imports.html).

+## <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. 


This might flow better:

Cats and Scalaz have the same goal: to facilitate pure functional programming in Scala applications. However, the underlying core strategy is different;

edmundnoble · 2017-09-14T17:16:37Z

docs/src/main/tut/faq.md

+
+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. 
+
+Based on this core strategy, Cats took a [modular](/cats/#modularity) approach and focuses on providing core, [binary compatible](/cats/#a-namebinary-compatibility-and-versioning), [approachable](/cats/#approachability) and [efficient](/cats/#efficiency) abstractions. It provides a welcoming and supportive environment for the [user community](https://gitter.im/typelevel/cats) governed 


cats takes*?

edmundnoble · 2017-09-14T17:17:15Z

docs/src/main/tut/faq.md

+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. 
+
+Based on this core strategy, Cats took a [modular](/cats/#modularity) approach and focuses on providing core, [binary compatible](/cats/#a-namebinary-compatibility-and-versioning), [approachable](/cats/#approachability) and [efficient](/cats/#efficiency) abstractions. It provides a welcoming and supportive environment for the [user community](https://gitter.im/typelevel/cats) governed 
+by the [typelevel code of conduct](https://typelevel.org/conduct). It also takes great effort in supplying a comprehensive and beginner-friendly [documentation](/cats/#documentation). 


I'm really not sure we can say this. I don't know where else we say this in the docs but I really don't think it's the case.

Not sure which part you are referring to, is it "great effort" or "comprehensive" or "beginner-friendly"?

edmundnoble · 2017-09-14T17:17:44Z

Eh slightly too late ;)

kailuowang · 2017-09-14T17:27:18Z

@edmundnoble no worries, I will submit another PR to address your feedback.

edmundnoble · 2017-09-14T17:30:24Z

Thanks, we also had some discussion on "comprehensive" and "great effort" in the cats gitter room.

kailuowang · 2017-09-14T17:58:20Z

@edmundnoble I would've been hesitant to say that myself, but the recent trend of contributions on the documentation side is really encouraging (20+ documentation PRs in the last 30 days).
@LukaJCB is really taking the initiatives on documentation (and other stuff too, thanks again @LukaJCB) on #1801
We are definitely not there yet, but I think we are making good progress. Maybe the language can be improved a bit. How would you phrase it?

kailuowang added 7 commits September 7, 2017 13:55

Update faq.md

3e1b42c

With @alexandru's consent, I adapted some content of a reddit comment of his to this item.

typos

5eff431

typo

ae0ca84

typo

9255b22

Update faq.md

aee5a6d

Update faq.md

cc98cc2

Update faq.md

d8d6656

kailuowang added the in progress label Sep 8, 2017

kailuowang requested review from stew, milessabin, non, ceedubs and adelbertc September 8, 2017 14:40

ceedubs reviewed Sep 8, 2017

View reviewed changes

kailuowang added 2 commits September 8, 2017 12:45

feedback

929c95b

Update faq.md

9d83e02

kailuowang added 2 commits September 8, 2017 13:09

Update faq.md

a64d2f4

Update faq.md

24c43d1

LukaJCB reviewed Sep 8, 2017

View reviewed changes

Update faq.md

24268e6

longcao reviewed Sep 8, 2017

View reviewed changes

kailuowang added 2 commits September 8, 2017 14:27

Update faq.md

fdb4e7f

Update faq.md

c2a1e27

ceedubs approved these changes Sep 12, 2017

View reviewed changes

kailuowang merged commit 7c74048 into master Sep 14, 2017

kailuowang deleted the faq-scalaz branch September 14, 2017 17:06

kailuowang removed the in progress label Sep 14, 2017

edmundnoble reviewed Sep 14, 2017

View reviewed changes

kailuowang added the documentation label Sep 14, 2017

kailuowang mentioned this pull request Sep 14, 2017

polishing FAQ #1912

Closed

kailuowang added this to the 1.0.0-RC1 milestone Oct 13, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

added FAQ item diff between cats and scalaz #1901

added FAQ item diff between cats and scalaz #1901

kailuowang commented Sep 8, 2017

ceedubs left a comment

ceedubs Sep 8, 2017

ceedubs Sep 8, 2017

codecov-io commented Sep 8, 2017 •

edited

Loading

kailuowang commented Sep 8, 2017

LukaJCB Sep 8, 2017

longcao Sep 8, 2017

johnynek commented Sep 14, 2017

edmundnoble Sep 14, 2017

edmundnoble Sep 14, 2017

edmundnoble Sep 14, 2017

kailuowang Sep 14, 2017 •

edited

Loading

edmundnoble commented Sep 14, 2017

kailuowang commented Sep 14, 2017

edmundnoble commented Sep 14, 2017

kailuowang commented Sep 14, 2017


		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](/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](/cats/#modularity) approach and focuses on providing core, [binary compatible](/cats/#a-namebinary-compatibility-and-versioning), [approachable](/cats/#approachability) and [efficient](/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](/cats/#documentation).


		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.

		Based on this core strategy, Cats took a [modular](/cats/#modularity) approach and focuses on providing core, [binary compatible](/cats/#a-namebinary-compatibility-and-versioning), [approachable](/cats/#approachability) and [efficient](/cats/#efficiency) abstractions. It provides a welcoming and supportive environment for the [user community](https://gitter.im/typelevel/cats) governed

added FAQ item diff between cats and scalaz #1901

added FAQ item diff between cats and scalaz #1901

Conversation

kailuowang commented Sep 8, 2017

ceedubs left a comment

Choose a reason for hiding this comment

ceedubs Sep 8, 2017

Choose a reason for hiding this comment

ceedubs Sep 8, 2017

Choose a reason for hiding this comment

codecov-io commented Sep 8, 2017 • edited Loading

Codecov Report

kailuowang commented Sep 8, 2017

LukaJCB Sep 8, 2017

Choose a reason for hiding this comment

longcao Sep 8, 2017

Choose a reason for hiding this comment

johnynek commented Sep 14, 2017

edmundnoble Sep 14, 2017

Choose a reason for hiding this comment

edmundnoble Sep 14, 2017

Choose a reason for hiding this comment

edmundnoble Sep 14, 2017

Choose a reason for hiding this comment

kailuowang Sep 14, 2017 • edited Loading

Choose a reason for hiding this comment

edmundnoble commented Sep 14, 2017

kailuowang commented Sep 14, 2017

edmundnoble commented Sep 14, 2017

kailuowang commented Sep 14, 2017

codecov-io commented Sep 8, 2017 •

edited

Loading

kailuowang Sep 14, 2017 •

edited

Loading