typelevel / typelevel/typelevel.github.com
Curated projects
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- HTML
- Sterne
- 42
- Forks
- 115
- Ø Merge
- 5 T. 5 Std.
- Gemergte PRs (30 T.)
- 7
Beschreibung
This is partly prompted by some thoughts after my tweet in response to the question of how to improve Scala adoption.
Trusted cohesive library ecosystem. A lot of library usage is built on trust, most folks have been bitten at one points by a lib with some gotchas. This is why I think building trust and branding of libs with shared ethos is very important.
It feels like the typelevel projects page could benefit by curating the functionality provided by the libraries in question. An example of the type of curation I think could be beneficial would be https://github.com/lauris/awesome-scala or https://github.com/rust-unofficial/awesome-rust, in that libraries are grouped based on functionality provided.
An example hierarchy could be:
"Web Server":
- "http4s"
- "Finch"
"HTTP Client":
- "fetch"
- "Hammock"
- "http4s"
"JSON":
- "argonaut-shapeless"
"Functional Reactive Programming":
- "cats-effect"
- "fs2"
- "monix"
Database:
- "doobie"
"Front End":
- "OutWatch"
Configuration:
- "Ciris"
- "Extruder"
- "PureConfig"
Serialization:
- "scodec"
"Science and Data Analysis":
- "Algebird"
- "coulomb"
- "Frameless"
- "Libra"
- "spire"
- "squants"
"Testing":
- "cats-scalatest"
- "ScalaCheck"
- "scalacheck-shapeless"
- "Specs2"
- "discipline"
"Linked Data":
- "banana-rdf"
"Generic Programming":
- "shapeless"
"Command Line":
- "decline"
"Extensions":
- "cats"
- "cats-tagless"
- "eff"
- "kittens"
- "monocle"
- "mouse"
- "refined"
- "singleton-ops"
"Misc":
- "algebra"
- "paiges"
- "scala-steward"
- "scala-exercises"
- "Scoverage"
"Macros and Compiler Plugins":
- "export-hook"
- "imp"
- "kind-projector"
- "Machinist"
- "macro-compat"
- "simulacrum"
- "TwoTails"
Hopefully this would make it easier to navigate the typelevel ecosystem and find the correct library for the job.
The following projects have been removed, based on lacking recent commits, or being known to be unsupported:
- Alleycats - redirects to cats.
- shapeless-contrib - no commits in 3 years.
- catalysts - can't decipher what the intended use of this project is? Is it a way of know which scala version is being used at runtime?
- structures - not updated in 5 years.
- tut - README suggests using mdoc
tut is deprecated. Please switch to mdoc. See the migration guide.. - CaseClassy - project abandoned.
- Sonic - 3 years since last commit.
Notes
If there are any analytics available for the typelevel website. It would be very useful to know how much the projects page is used.
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne mit der projects-Seite auf typelevel.org und vergleiche ihren aktuellen Inhalt mit den in diesem Issue vorgeschlagenen funktionsbasierten Kategorien und Projektentfernungen. Als erledigt gilt die Aufgabe, wenn die Seite eine nützliche kuratierte Gruppierung präsentiert, die aufgelisteten nicht unterstützten Projekte ausschließt und alle verfügbaren Erkenntnisse aus der Analytics widerspiegelt; die zu aktualisierende Repository-Datei wird hier nicht angegeben.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- html, scala
- Bereich
- content, documentation
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100