Quill VS Scala.js

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

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?

Just as an example, say you are using quill ( https://getquill.io/ ) to query your database.

I think Quill is the closest to your request: https://github.com/zio/zio-quill

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.

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).

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.

Akka HTTP, Cats, Quill, ninny, Monix Observable, mill.

`$` does mean end of input in Java, unless you explicitly ask for multiline mode. In the latter case it means `(?=$|\n)` if also in Unix-lines mode, and the horrible `(?=$|(?I wrote a compiler from Java regex to JavaScript RegExp, in which you'll find that particular compilation scheme [1].

[1] https://github.com/scala-js/scala-js/blob/eb160f1ef113794999...

Links: - https://dotty.epfl.ch/ - https://scala-native.org/en/stable/ - https://www.scala-js.org/ - https://typelevel.org/ - https://zio.dev/ - https://github.com/scala-native/scala-native/pull/3120 - https://github.com/lampepfl/dotty/pull/16517 - https://dotty.epfl.ch/docs/reference/experimental/index.html - https://scala-cli.virtuslab.org/ - https://scalameta.org/metals/ - https://docs.scala-lang.org/scala3/guides/migration/compatibility-intro.html - https://www.scala-lang.org/blog/2023/04/18/faster-scalajs-development-with-frontend-tooling.html - https://www.scala-lang.org/blog/2022/08/17/long-term-compatibility-plans.html

> Scala choices were directly dictated by JVM

Initially, yes. But Scala has evolved beyond the JVM, with Scala.js [1] being rock-solid, and Scala Native [2] under development. Neither are truly hampered by the initial JVM roots of Scala.

> Scala gives you a better horse

Weird analogy ;)

[1] https://www.scala-js.org/

Have you had a look at Scala.js yet? Also see "Scala.js for JavaScript developers." and "Tour of Scala."

What does that have to do with language size? It also compiles to js https://www.scala-js.org/ and native https://scala-native.org/en/stable/

Here's a hybrid option: Scala.js. Yes, it is about building web applications but in Scala. You can retain the HTML/CSS/JS knowledge you have but build web applications from a typesafe and powerful language: Scala

The compiler crash in question affects another feature that we would like to merge for the benefit of all users, namely https://github.com/scala-js/scala-js/pull/4735. Keeping 2.11 means that testing and shipping that feature is much more difficult, even for 2.12+ users only. It's not just "to fix a compiler crash".

TS is more in the "mixed feelings" department, imho.

I would take Scala.js anytime instead. (If I would need to do front-end ever again).

https://www.scala-js.org/