News for hackers. Stuff that matters.
Re:Scala: Where it came from, Where it's going by weego on Tuesday March 17, 2015 @12:41PM (#9219188)
I started off learning Scala in a 2 man band startup for 3 or so years and moving to a company with 20+ full time Scala developers was a huge eye opener. All the things that hooked me about Scala like taking advantage of its relatively un-opinionated structure to be quite expressive with how you build things turned out to be major pain points when you scale out into teams who rotate developers on frequent basis.

I think I'm paraphrasing something I read about Twitter when I say that everyone who uses Scala ends up taking a subset of the language they are happy with, and that ends up being the case at a team level and intra-person level too (starting at the new place ended up with some very frosty pair programming sessions).

Add to that the necessity to cross train every developer who joins because recruitment is hard enough without specifying experience in a relatively obscure language and you have a constant cycle of painful recruitment, on-boarding and maintenance.

Re:Scala: Where it came from, Where it's going by evgen on Tuesday March 17, 2015 @12:50PM (#9219267)
Wow, you could s/Scala/Perl/g in there and it would have described the entire Perl5 era...
Re:Scala: Where it came from, Where it's going by azmenthe on Tuesday March 17, 2015 @01:12PM (#9219470)
Or C++ at any point in it's history. I guess it's the burden of being multi-paradigm.

Edit: Looks like zak_mc_kracken beat me to it. Which I think just makes the point even more obvious

Re:Scala: Where it came from, Where it's going by zak_mc_kracken on Tuesday March 17, 2015 @01:09PM (#9219441)
Or C++. The whole "But you can only use a subset of the language if you want" part will particularly resonate with anyone who wrote C++ in the past couple of decades.

And this argument is nonsense.