4 ms·
I have written Scala on several large projects( and Play framework) One of the problems with Scala is that there are a thousand ways to do everything, which is
by tenpoundhammer 13y ago
I have written Scala on several large projects( and Play framework)
One of the problems with Scala is that there are a thousand ways to do everything, which is often insanely confusing to a lot of people. And another I think is that people try to teach scala like they teach other OO languages and it just doesn't work.
Scala is not that hard once you boil it down the set of features that your team wants to use.
After learning Scala and then teaching it to several java developers, I believe I could get someone productive in Scala in 5-10 hours.
There are a couple of cognitive hurdles, and a few difficult to implement features in the super deep realm of coding, but it's really not that hard.
- hackerboos 13y ago>I believe I could get someone productive in Scala in 5-10 hours. Write an book on leanpub. You'll make a fortune...
- tenpoundhammer 13y agoI don't think I could do it with a book. I think I could do it with a combination of lecture, exercises, and a little Q&A. At least that has worked in the past.
- kodablah 13y agoI agree that it's hard to trim down the feature set you want a team to use, but for individual development it is really nice. I like building a solution to my problem and whittling it down to clear and concise code. The resulting can be information dense if you let it, but I like it. I find myself spending lots of time reading Akka and Spray docs just to output a few characters. I can understand why highly volatile software can be tough in Scala. But I appreciate the concept of expending a lot of thought on a minimal amount code that is easy to read.
- tenpoundhammer 13y agoI love me some matchers with cases and gaurds. You can make some normally gnarly looking and hard to read decision trees into really concise easy to read cases.
- beefhash 13y ago>Scala is not that hard once you boil it down the set of features that your team wants to use. Isn't that, essentially, what you already have to do with C++ to keep that manageable? If so, why not go straight for C++ and get improved performance in return?
- tenpoundhammer 13y agoC++ is not a functional language and it doesn't run on the jvm. So this is more of a question of what are you looking in a programming langauge. For teams that are already heavily invested in the JVM it's very attractive. There are also a ton of advantages in the multi-processing aspects of scala.