News for hackers. Stuff that matters.
Re:Scala Best Practices by the_af on Friday October 31, 2014 @11:20AM (#8539181)
When you think about them, a lot of those rules aren't Scala-specific (though some are). So you could just as well say "most programming languages are giant tumors of complexity".

For example, if you write Java, most (or similar, or even more complex) rules apply.

Re:Scala Best Practices by bkeroack on Friday October 31, 2014 @12:55PM (#8539758)
"Java is just is bad" is not a ringing endorsement.
Re:Scala Best Practices by the_af on Friday October 31, 2014 @01:46PM (#8540059)
Heh. I'm not one of them, but a lot of people think Java would be mostly fine with just minor updates.

In any case, I chose Java as an example because (sadly) it's what I'm forced to use in my day job, with some Scala side-projects (thankfully!). But I didn't mean to single Java out: a lot of the advice applies in general to software design, regardless of language. You know, "choose the right abstraction", "beware concurrency", "name things wisely", etc.