mdoc
cats
mdoc | cats | |
---|---|---|
4 | 43 | |
387 | 5,182 | |
0.5% | 0.6% | |
8.4 | 8.8 | |
20 days ago | 1 day ago | |
Scala | Scala | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mdoc
- Optimal decision-making with examples built using scala
-
Friction-less scala - Tell us what is causing friction in your day-to-day life with Scala
Literally what scaladoc is, it comes with sbt. Although, it's better when enhanced with mdoc so that you get the standard microsite template like these. It would be nice to have an sbt serveDocs and if everyone would host their docs for external linking, but javadoc doesn't do that either.
-
A Scala rant
The good news is that scaladoc is produced by default by sbt and published by default. So you can often pull it from the same repository your library jar came from, extract it with zip, and read the docs. But that's also totally unnecessary - javadoc.io allows you to put in your module info and serves the docs for you, so if there's an older version you can access the documentation this way. Rely on the type signatures, since they can't lie, whilst comments (including scaladoc comments) can. Honestly, library authors should be using mdoc and including examples on every public method, and that type of documentation is something you can almost always contribute to a project for a quick pr kudos.
-
The future of Scaladoc
I know it's not new but the "Snippet validation and results (mdoc)" features in mdoc are so cool. Really takes some of the tedium out of working with documentation since you can know that as you evolve your code the compiler will make sure you keep the docs in sync. Whole new level of Readme-Driven Development
cats
-
Beware of teammates who refactor code based on personal taste without proper documentation or completeness. Sounds familiar.
A functional programming library: https://typelevel.org/cats/
-
Is Scala worth learning in 2023?
Learn something that pays the bill first - nowadays it's Golang/Rust react/typescript. Then you can try some pure fp libs like fp-ts and fp-core.rs, and look through existing scala cats docs. If you'll feel bad about it - that's totally fine and expectable, fp takes a paradigm shift and not that many dev able to shift their brains way of thought due to basic psychological rigidity) (inability to change habits and to modify concepts/attitudes once developed). And that's purely a staffing and management issue - folks hired randoms out of the blue, and called 'em a team.
-
Going into year 2 of Software Development Foundation Degree, have a particular liking for OOP and SQL, any tips, info or pointers on where to go from there?
I'm sorry, but have you ever done functional programming for a real company, like in a functional programming language like Haskell, Scala, or F#? Have you ever used Scala cats or scalaz? Have you ever learned category theory and how to apply its abstractions in software? Listen u/judethedude2106 this person hasn't gone as far down the functional programming rabbit hole as I have. Beyond learning the basics like the difference between pure and impure functions, what are closures, what higher order functions are and the most common ones like .map, .filter, and .flatmap, the immutable collections like immutable linked lists and trees, and what a Monad is and common monads like those used for futures/promises, async programming, and Option (Some or None, which is used instead of null checking), the more advanced functional programming stuff like category theory based abstractions are totally useless for real jobs and is just a giant time suck. Don't waste years on functional programming, spend at most a few months on it and no more.
-
rsmonad: Monads in stable Rust (+ Applicative, Alternative, Functor, Monoid, ...)
As a former functional programmer in Scala, please do not go deep into the Category Theory programming. Scala has libraries like this one called "Cats", a cute shortened name for "Category Theory", but code that makes heavy use of these constructs is not understandable to other programmers. Other than using Monads as a design pattern for things like Options (which can be "Some" or "None"), Futures or Promises (which is used for asynchronous programming), and a few other things, please do not make heavy use of category theory constructs in real programming projects that will have other developers working on them. It is a rabbit hole that may be fun but is not super practical. Sure, write pure functions without side effects, but do not use the words "Bimonad", "Invariant Monoidal", and "Semigroup" in your code. The most common, practical application/use of functional programming is basic things like closures, .map, .filter, maybe chaining maps with like a .flatmap or whatever your programming language uses instead of chain or flatmap, and SQL that uses keywords like WHERE which can be represented in code by using a call to .filter. Like the place where these constructs are used most is in data processing like with SQL, ETL (Extract Transform, Load) jobs, Java's MapReduce on Hadoop, Scala's Apache Spark, and other data processing type things. Haskell is not a popular programming language in real world projects for a number of reasons and one of them is the heavy and sometimes impractical use of Category Theory.
-
Tmux, NeoVim, etc. to write pure Kotlin code?
At a previous job of mine we actually had an entirely pure Scala ecosystem using cats which instead uses typeclasses, referential transparency, and other FP concepts as the foundations for how to code. So a lot of flexibility to the language.
-
[E => *] Type
Thanks! It's used heavily here
- for comprehension and some questions
-
Ask HN: How has functional programming influenced your thinking?
I did work in Scala for a few years. We employed Cats[1], and even a bit of Matryoshka[2] though most of the work I do today is in Python.
Nowadays I think about computational requirements in terms of relations among behavioral dependencies. Like, "I want to perform operation O on input A and return a B. To do this, I'll need a way to a -> b and a way to b -> b -> b." I often pass these behavioral dependencies in as arguments and it tends to make the inner core of my programs pretty abstract and built up as layers of specificity.
Zooming out nearly all the way, it makes me feel tethered in a qualitatively unique way to certain deep truths of the universe. In a Platonic sense, invoking certain ideas like a monad make me feel like I'm approaching the divine or at least one instantiation of a timeless universal that operates outside of material existence.
I'd imagine some mathematicians might see the universe in a similar way - one where immortal relations between ontological forms exist beyond time and space and at the same time can be threaded through the material world by intellectual observation and when those two meet a beautiful collision occurs.
1. https://typelevel.org/cats/
2. https://github.com/precog/matryoshka
-
yet another post about type classes in Scala
Our second type class example attempted to illustrate one last perk: type safety at compile time. It did so with a simplified example of the cats core library for type safety equality comparison between objects. If you're not familiar with cats, go ahead and give it go.
- What are the design principles of Cargo?
What are some alternatives?
sbt-unidoc - sbt plugin to create a unified Scaladoc or Javadoc API document across multiple subprojects.
Scalaz - Principled Functional Programming in Scala
sbt-mima-plugin - A tool for catching binary incompatibility in Scala
Shapeless - Generic programming for Scala
sbt-revolver - An SBT plugin for dangerously fast development turnaround in Scala
ZIO - ZIO — A type-safe, composable library for async and concurrent programming in Scala
sbt-pack - A sbt plugin for creating distributable Scala packages.
ScalaTest - A testing tool for Scala and Java developers
coursier - Pure Scala Artifact Fetching
Monocle - Optics library for Scala
sbt-updates - sbt plugin that can check Maven and Ivy repositories for dependency updates
Scala Async - An asynchronous programming facility for Scala