This list would be a ton more useful if there were some metrics or indications for which libraries were included and why. Just as good, which were purposefully <i>not</i> included. And again, why.<p>This is pretty much <i>the</i> 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.
Also <a href="https://github.com/softprops/ls" rel="nofollow">https://github.com/softprops/ls</a> and <a href="https://github.com/velvia/links" rel="nofollow">https://github.com/velvia/links</a>
I've asked before but I'm going to try again: are there any resources out there for learning Scala that do not assume a Java background?<p>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?
It's interesting to see that most of these libraries are either web services or language support. Are client side apps for the (Oracle) JVM definitively over?
I wish people would stop creating scala libraries and frameworks, it just fragments the java community. Scala was a short term hack to fill in the gaps until Java has lambdas. Java does now and there's no need to keep scala separate, the syntactical sugar to remove some of the boilerplate to java is just not worth the fragmenting effect. We've seen much the same thing with python 2 and python 3, which differ in ways similar to java. We need to delete scala and delete python 3 and all get back to solving real problems.