News for hackers. Stuff that matters.
Re:Why or Why Aren’t You Using Scala? by mooism2 on Friday July 11, 2014 @10:14AM (#8020202)
1. The type system is too complicated.

2. It's difficult to find implicits. If I am looking for a Haskell typeclass instance, I know it will probably be defined either in the same module as the type, or the same module as the typeclass. I couldn't work out where to find implicits.

Re:Why or Why Aren’t You Using Scala? by papauschek on Saturday July 12, 2014 @07:38PM (#8026120)
It's easy to get lost in the type system if you use type-complex frameworks like Slick.

Right now, there are a lot of frameworks to choose from and to evaluate. And there are a lot of "experiments" going on. I think that this will improve as the community matures and settles on fewer ways to do things.

We've been using Scala now for 18 months in production, and I sometimes feel that library designers need to step back and try to not overuse the power of the language.

Re:Why or Why Aren’t You Using Scala? by imosquera on Friday July 11, 2014 @11:19AM (#8020570)
Yah, it's not easy to find the implicit and definitely need to use a solid IDE to track these things down. I've gained enough experience now that I can track things down quickly but it's taken me a while to get here. I wonder if others will be willing to do the same or adoption of the language will stagnate.
Re:Why or Why Aren’t You Using Scala? by frowaway001 on Friday July 11, 2014 @10:42AM (#8020338)
> I know it will probably be defined either in the same module as the type, or the same module as the typeclass

Just like in Scala.

> I couldn't work out where to find implicits.

Click on the squiggly lines? (Or hover over the indicator next to the line numbers?)