µTest
Quill
Our great sponsors
µTest | Quill | |
---|---|---|
2 | 15 | |
478 | 2,136 | |
-0.6% | 0.0% | |
4.2 | 9.1 | |
6 days ago | 6 days ago | |
Scala | Scala | |
- | Apache License 2.0 |
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.
µTest
-
From First Principles: Why Scala?
Let's clarify some points for folks not so familiar with Scala.
> * Scala minor version are binary incompatible, so maintaining Scala projects is a big pain. Upgrading Spark from Scala 2.11 to Scala 2.12 was a massive undertaking for example.
Scala just chose a strange naming scheme. Other languages would have just increased their major version instead. The scala minor version is increased every few years and not every month or so.
> * Scala has tons of language features and lets people do crazy things in the code.
Actually, that's not true. Or rather: compared to what language?
Scala has surprisingly few language features, but the ones it has are very flexible and powerful. Take Kotlin for example. It has method extensions as a dedicated feature. Scala just has implicits which can be used for method extension.
> * Scalatest is stil used by most projects and is annoying to use, as described here: https://github.com/lihaoyi/utest#why-utest. The overuse of DSLs in Scala is really annoying.
I agree with the overuse of DSLs. Luckily that got much better, but older libraries like scalatest still suffer from that.
> * Li's libs (os-lib, upickle, utest) have clean public interfaces, but most Scala ecosystem libs are hard to use, see the JSON alternatives for examples
I think that just comes from using the library in a non-idiomatic way. In most applications, you will need to use the whole json anyways, and then you use (or can use) circe like that:
{
Quill
-
Dear Sir, You Have Built a Compiler (2022)
https://github.com/zio/zio-quill
This library does exactly what you prescribe. Pretty sure under the hood it's using macros with string templates
- Sketch of a Post-ORM
-
Why use Spark?
But I can connect to Postgress with something like Quill and run sophisticated queries to fetch data. Which then got me thinking, what is the difference between using Spark to connect to the database and using something like Quill or your normal pure JDBC driver?
-
What's the point of opaque type aliases (and are they actually sound)?
Just as an example, say you are using quill ( https://getquill.io/ ) to query your database.
- I want to move to Scala 3, but I'm not sure what libraries to use
-
Query DSL in Scala ?
I think Quill is the closest to your request: https://github.com/zio/zio-quill
-
Doobie tutorial: databases and pure FP in Scala
If this still looks like too much hassle, you can always go a bit higher-level and use something like Quill, which is also a powerful approach that uses a different, more ORM-like style.
-
Ask HN: What cutting-edge technology do you use?
I'm using it mostly for full-stack web development with ScalaJS (https://www.scala-js.org) in the frontend (https://outwatch.github.io/docs/readme.html) and in the backend with AWS lambdas.
The ecosystem is currently in the process of porting all the libraries to Scala 3. So if you're new to Scala, I'd recommend to start with Scala 2, which is rock-solid and already very powerful.
I never worked with SQLAlchemy. But on the scala database side, popular libraries are Doobie (https://tpolecat.github.io/doobie) and Quill (https://getquill.io). Keep in mind that these are for Scala on the JVM. On the ScalaJS side I'm using the javascript library pg. But I'd like to try if it works well with Prisma soon.
The nice thing about ScalaJS is, that you can use Javascript libraries. And if there are typescript facades, then you can transpile these to Scala and use them in a type safe way (https://scalablytyped.org).
-
Fp libraries that target scala 3 exclusively?
I know that libraries like Scodec and shapeless were rewritten practically from scratch for Scala 3, taking advantage of the next syntax and internals, as well as protoquill - a Scala 3 implementation of Quill.
-
Best Scala framework / libraries out there ?
Akka HTTP, Cats, Quill, ninny, Monix Observable, mill.
What are some alternatives?
ScalaMock - Native Scala mocking framework
Slick - Slick (Scala Language Integrated Connection Kit) is a modern database query and access library for Scala
Diffy
doobie - Functional JDBC layer for Scala.
scalaprops - property based testing library for 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.
Scala Test-State - Scala Test-State.
Phantom - Schema safe, type-safe, reactive Scala driver for Cassandra/Datastax Enterprise
Gatling - Modern Load Testing as Code
Clickhouse-scala-client - Clickhouse Scala Client with Reactive Streams support
Scalive - Connect a Scala REPL to running JVM processes without any prior setup
zio-protoquill - Quill for Scala 3