typelevel / typelevel/typelevel.github.com
Curated projects
Personne n'a encore pris cette issue.
- Langage dominant
- HTML
- Étoiles
- 42
- Forks
- 115
- Merge moyen
- 5 j 5 h
- PR mergées (30 j)
- 7
Description
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.
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par la page des projets de typelevel.org et comparez son contenu actuel aux catégories proposées fondées sur les fonctionnalités et aux suppressions de projets proposées dans cette issue. La tâche est considérée comme terminée lorsque la page présente un regroupement utile et organisé, exclut les projets non pris en charge répertoriés et reflète les éventuels résultats disponibles de l’Analytics ; le fichier du repository à mettre à jour n’est pas identifié ici.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- html, scala
- Domaine
- content, documentation
- Type d'issue
- Documentation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100