cats
Slick
Our great sponsors
cats | Slick | |
---|---|---|
43 | 17 | |
5,163 | 2,636 | |
0.7% | 0.1% | |
8.9 | 8.6 | |
7 days ago | 4 days ago | |
Scala | Scala | |
GNU General Public License v3.0 or later | BSD 2-clause "Simplified" License |
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.
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.
-
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?
Slick
- How many people/companies are fully on Scala 3?
-
First Slick prerelease for Scala 3!
Made a PR on slick to document this https://github.com/slick/slick/pull/2760 (workaround is quite easy, you can just define def tupled = (apply _).tupled in the companion object of the case class and it will also compile for all Scala versions).
-
Sketch of a Post-ORM
The Scala ecosystem has a few ways to do composable type-safe query building, e.g. Slick[0] or more recently Quill[1]. . I believe both also have ways to do compile-time string interpolation (e.g. sql"""select * from users where id = ${user.id}""") which generate prepared statements (I know Slick does prepared statements. Quill has similar macros but I haven't looked into how safe they are to use).
-
Slick 3.5.0-M3 has been released
Release notes at https://github.com/slick/slick/releases/tag/v3.5.0-M3
-
Database abstraction library which allows a clean domain model
With all this in mind, I landed at the first candidate: slick from https://scala-slick.org/ that you all probably know.
-
Scala 3 migration: 7 benefits that outweigh the risks
I think Slick's current priority is also getting in Scala 3 support: https://github.com/slick/slick/issues/2177
-
Slick 3.4.x is here!
Future releases might not be announced here. To get notified, go to https://github.com/slick/slick, click the Watch dropdown button at the top, select Custom, check Releases, and click Apply.
-
Is there any good resource for learning Slick (3.x)?
https://github.com/slick/slick/pull/2097 now I use slightly lower version of slick so this might be an upgrade that resolves (I do recall using it in 21 and it was still buggy and I filed a ticket, which I cannot find at the moment), but given a complex enough query (we have one in PROD which has tons of flexibility in terms of filters that can be passed in) but it also makes for complex code.
-
Slick 3.4.0 is imminent
I started writing a reply but then I realized it would be long and depends on exactly what you mean, so maybe it's better to post the question in https://github.com/slick/slick/discussions/categories/questions?
-
Scala: A Love Story
I purchased the very entertaining book Seven Languages in Seven Weeks. Although I found Haskell fascinating and tempting, I knew it was unrealistic to introduce it in our company. Scala on the other hand looked like it could be the holy grail: All the characteristics I was looking for, no need to abandon the JVM and its cornucopia of tools and libraries, and the possibility for coexistence with Java and therefore incremental adoption. After implementing some simple programs to identify any immediate risks of committing to the language and its ecosystem, I started to introduce Scala in customer projects. Luckily, I was fortunate enough to work with open-minded, curious, and ambitious team members who were also experienced enough to appreciate the benefits of the language. We immediately applied our experience with functional programming, and embraced immutability. Libraries like Slick and Akka HTTP (we actually started out with its predecessor, Spray) made building database-backed REST services a breeze. And the resulting code was robust and highly maintainable. Scala's expressive type system and type inference made it easy to build a restrictive, consistent domain model without bloating the code. There was virtually no overhead. Any boilerplate could be easily abstracted out. In the end, the application code felt natural, concise and elegant. Programming was fun again.
What are some alternatives?
Scalaz - Principled Functional Programming in Scala
doobie - Functional JDBC layer for Scala.
Shapeless - Generic programming for Scala
Quill - Compile-time Language Integrated Queries for Scala
ZIO - ZIO — A type-safe, composable library for async and concurrent programming in Scala
ScalikeJDBC - A tidy SQL-based DB access library for Scala developers. This library naturally wraps JDBC APIs and provides you easy-to-use APIs.
ScalaTest - A testing tool for Scala and Java developers
Squeryl - A Scala DSL for talking with databases with minimum verbosity and maximum type safety
Monocle - Optics library for Scala
Clickhouse-scala-client - Clickhouse Scala Client with Reactive Streams support
Scala Async - An asynchronous programming facility for Scala
Sorm - A functional boilerplate-free Scala ORM