Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I agree with the other commenters that there are plenty of people working on Scala (and arguably odersky is a much better researcher than he is a maintainer) that I wouldn't worry about people maintaining/upgrading Scala.

I do think 2.12 (and 2.11 before it) either had unrealistically optimistic deadlines or suffer from poor project management. 2.12 has slipped by well over a year at this point, which is sad for frameworks like Spark which are going to stick to 2.11 for their next MV cycle.



Scala 2.12 M4 still manages to leave experts perplexed,

https://groups.google.com/forum/#!topic/scala-internals/lv4s...

The fact that the 2.11.x series had a number of "dead on arrival" minor releases also confirms: better not to hurry to adopt a new Scala release.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: