3 ms·

Nobody should be recommending Slick to anyone for new projects. Slick will not be supported in the future.

solicode 6y ago
I've heard that too but I think there are at least efforts to support Scala 3. Having said that I think Quill looks nicer (https://getquill.io/ https://getquill.io/) if you want a DSL like that.
- valzam 6y ago
  I haven't used it heavily but one of our newer microservices uses Quill for read-only access to Postgres. I have found it to be great to work with, to combination of "just use case classes" and a DSL that feels like writing SQL is pretty nice.
  - still_grokking 6y ago
    You can have Quill syntax for Doobie nowadays: https://tpolecat.github.io/doobie/docs/17-Quill.html https://tpolecat.github.io/doobie/docs/17-Quill.html That's by far the best DB access layer I've ever worked with.
yw3410 6y ago
I seem to remember Stefan Ziegler asking around the channels about questions relating to how to do certain features to uplift Slick. Don't know if anything came out of it.
thelittlenag 6y ago
Lightbend is planning to end support and development of Slick? This is the first I've heard of this. Can you point me towards what they've said?
- merb 6y ago
  they never said that, but it's basically abadonware. look at the commit history: https://github.com/slick/slick/commits/master https://github.com/slick/slick/commits/master you can also look at the contributors page: https://github.com/slick/slick/graphs/contributors https://github.com/slick/slick/graphs/contributors the guys who primarly contributed to it basically left lightbend, and in 2019 he shifted his priorities. it only had 28 commits since 2020 (including merge commits and changes to the build process) it's basically dead until somebody steps up.
  - zmmmmm 6y ago
    > 28 commits since 2020 wow, the bar for "not dead" is really high these days :-)
    - merb 6y ago
      well as said 28 commits, NOT ALL were code. MOST of them were basically "fix build"/update dep. so basically the project did not change for over a year. AND 2019 wasn't really better. 3.3.2 (3.3.3 was mid 2020) was in JUNE 2019 and 3.3.0 was at the beginning of 2019. there won't be a 3.4 anytime soon, if nobody steps up and starts maintaining it, there won't be a 3.4 at all. slick is heavy on macros it will not survive scala 3
      - still_grokking 6y ago
        Well, that would streamline nicely the options for DB libs in Scala… Doobie (optionally with Quill Syntax) would be left and become likely the "Hibernate of Scala-Land". That's not too bad news imho.

I've heard that too but I think there are at least efforts to support Scala 3. Having said that I think Quill looks nicer (https://getquill.io/ https://getquill.io/) if you want a DSL like that.

valzam 6y ago
I haven't used it heavily but one of our newer microservices uses Quill for read-only access to Postgres. I have found it to be great to work with, to combination of "just use case classes" and a DSL that feels like writing SQL is pretty nice.
- still_grokking 6y ago
  You can have Quill syntax for Doobie nowadays: https://tpolecat.github.io/doobie/docs/17-Quill.html https://tpolecat.github.io/doobie/docs/17-Quill.html That's by far the best DB access layer I've ever worked with.

yw3410 6y ago

I seem to remember Stefan Ziegler asking around the channels about questions relating to how to do certain features to uplift Slick. Don't know if anything came out of it.

thelittlenag 6y ago

Lightbend is planning to end support and development of Slick? This is the first I've heard of this. Can you point me towards what they've said?

merb 6y ago
they never said that, but it's basically abadonware. look at the commit history: https://github.com/slick/slick/commits/master https://github.com/slick/slick/commits/master you can also look at the contributors page: https://github.com/slick/slick/graphs/contributors https://github.com/slick/slick/graphs/contributors the guys who primarly contributed to it basically left lightbend, and in 2019 he shifted his priorities. it only had 28 commits since 2020 (including merge commits and changes to the build process) it's basically dead until somebody steps up.
- zmmmmm 6y ago
  > 28 commits since 2020 wow, the bar for "not dead" is really high these days :-)
  - merb 6y ago
    well as said 28 commits, NOT ALL were code. MOST of them were basically "fix build"/update dep. so basically the project did not change for over a year. AND 2019 wasn't really better. 3.3.2 (3.3.3 was mid 2020) was in JUNE 2019 and 3.3.0 was at the beginning of 2019. there won't be a 3.4 anytime soon, if nobody steps up and starts maintaining it, there won't be a 3.4 at all. slick is heavy on macros it will not survive scala 3
    - still_grokking 6y ago
      Well, that would streamline nicely the options for DB libs in Scala… Doobie (optionally with Quill Syntax) would be left and become likely the "Hibernate of Scala-Land". That's not too bad news imho.