News for hackers. Stuff that matters.
Re:Scala: the Case for Correctness by jakozaur on Tuesday October 14, 2014 @10:11PM (#8456863)
Scala gets a lot of things right by default. Also it got a lot of flexibility and power. Almost "a framework" to write other languages within the language.

Use it every work day for over two years... Like a lot, but sometimes wishes it would be a bit simpler and more aesthetic.

Re:Scala: the Case for Correctness by rld on Tuesday October 14, 2014 @11:24PM (#8457040)
What do you mean by "more aesthetic"? As in syntax?
Re:Scala: the Case for Correctness by rco8786 on Tuesday October 14, 2014 @11:36PM (#8457060)
Speaking for OP here, but yea. The simple examples are definitely simple. But in practice it can get out of hand really quick.

The type system is crazy powerful, but that also means it's crazy complex.

Re:Scala: the Case for Correctness by jakozaur on Wednesday October 15, 2014 @01:53AM (#8457315)
There are sometimes too many ways of doing the same thing.

E.g.

- syntax: def func() { and def func(): Unit = {

- collection library

Re:Scala: the Case for Correctness by frowaway001 on Wednesday October 15, 2014 @12:25PM (#8459370)
> def func() {

That's already deprecated (under -Xfuture):

  <console>:1: warning: Procedure syntax is deprecated. 
  Convert procedure `func` to method by adding `: Unit =`.