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 not included. And again, why.
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.
Agreed, it's pretty much the opposite of "curated" as it stands, especially since it's hard to believe the creators of the list studied carefully the sources of all these frameworks in order to determine their awesomeness.
The list is open source and community driven. It means that everyone can improve it and suggest edits. There has already been 19 pull requests with additions and deletions.
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.
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?
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've been working with scala for about 1.5 years. My background previously was mostly Python & R for the previous 10 years although I had been working w/ Java a little here and there for about a year prior to switching to 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.
Coursera has a couple of Scala courses: try the introductory one "Functional Programming Principles in Scala". I'm not sure when it will be offered next, but they've given it a few times already. It doesn't require any Java knowledge.
The things you identified you will need to know and would be proficient knowing them. JDBC not so much but depending on the libs you use, you could be using it indirectly. Same story with maven, knowing how to look up stuff on mavencentral will help but beyond that you don't need to care.
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.
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.
> Scala was a short term hack to fill in the gaps until Java has lambdas.
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.
taeric|11 years ago
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.
zak_mc_kracken|11 years ago
lauriswtf|11 years ago
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.
facorreia|11 years ago
bkeroack|11 years ago
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?
jghn|11 years ago
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.
MaysonL|11 years ago
kev009|11 years ago
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.
DCKing|11 years ago
hnriot|11 years ago
DCKing|11 years ago
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.
x_42_123|11 years ago
http://www.youtube.com/watch?v=uiJycy6dFSQ