Capabilities appear to be the hot topic in the Scala community right now.
When it comes to Scala interviews, the trick isn't just solving problems - it's solving them the Scala way.Interviewers are often less interested in whether you can code something and more curious about how you think, use language features, and write clean functional code. In this article, I'll walk through three interview-style Scala questions. Each question is designed to test a different dimension of your Scala skill set - from string manipulation to functional collections and stack-based problem solving.
Slick (short for Scala Language Integrated Connection Kit) is one of the most widely used libraries in the Scala ecosystem for functional, type-safe, and composable database access. It provides a clean DSL for querying SQL databases while staying true to Scala's functional style. In this article, we'll explore: What Slick is and why it matters How to set up a Slick environment in a Scala project Basic CRUD operations with examples Slick in Play Framework vs. standalone Scala apps Common pitfalls and best practices
This is technically a hotfix patch release for 1.20.0, which was discovered to be severely broken, and was therefore never announced. These release notes therefore present it as a "minor release" compared to 1.19.0. This release mainly comes with many performance improvements to the WebAssembly and JavaScript backends alike. As of this writing, the latest versions of Firefox (since v131), Safari (since v18.4) and Chrome (since v137) support all the WebAssembly features required to run Scala.js-on-Wasm.
One of the most famous and longstanding limitations of the Cats Effect IO type (and the Cats generic typeclasses) is the fact that the only available error channel is Throwable. This stands in contrast to bifunctor or polyfunctor techniques, which add a typed error channel within the monad itself. You can see this easily in type signatures: IO[String] indicates an IO which returns a String or may produce a Throwable error ( Future[String] is directly analogous).
Workflows4s is a Scala library for modeling and running workflows in a type-safe, composable, and functional way. It allows developers to represent long-running business processes or system orchestrations as pure code.