This is pretty much the reason folks go with full stack frameworks fairly often. Trying to determine which of the testing modules to pair with which authentication module and which ... is annoying.
Currently the list is just a work in progress, but I am certain that after several iterations of pull requests it will be up to date and useful.
At the least, common metrics that can be applied to various offerings would be neat. Possibly a qualifier such that you can't add an item unless it meets a threshold on a few criteria.
If you're going to claim this list is "curated" and the projects listed there are "awesome Scala", the least you can do is explain the criteria.
I have no Java experience (I'm primarily a Python developer) and therefore find most of the documentation difficult because I'm not at all familiar with the Java ecosystem (maven, jars, weird reverse-DNS naming convention for packages, JDBC, etc). Am I expected to first become a Java developer before I can even start with Scala?
I didn't encounter any difficulty picking up Scala - my main resources at the time were "Programming in Scala", poking around StackOverflow and my group's existing code base. If anything I think my background with Python & R helped as I was already familiar with a lot of the functional-ish approaches from those languages (e.g. lambdas, maps, etc)
As Kev009 pointed out, using something like IntelliJ helped immensely as well as it handles a lot of the boilerplate-y stuff.
I'll give IntelliJ another try, thanks.
As a counter example, I was up and running with Go in 15 minutes.
Knowing a little Java would help when calling into Java libs but an IDE like IntelliJ that can help you understand conversions would do well too.
A lot of people convert from languages like Perl and Ruby without tremendous difficulty. I can only recommend diving in to make a real assessment, prejudices and phobias will otherwise prevent understanding.
If you think this is true and not just trolling, you are extremely ignorant about Scala's history, Scala's aims and Scala's features. Scala is so much more than a better Java, this statement is beyond ridiculous.
https://github.com/zenbowman/slickint
And even then, I think I by far prefer raw SQL to Slick. If you stick to the standard Scala libraries, they are pretty well designed, and I second taking the Functional progamming in scala course. There is some discussion of the toolchain in Lecture 0 of that course.
I just found writing the classes painful so I wrote slickint to deal with generation of classes, and it was reasonable after that.