b.) A community that upgrades libraries (your dependencies) to every new RC candidate - even when only fixing bugs. So if you have a show stopper bug you need to upgrade to the newest RC breaking all your other dependencies.
Either a. and b. would be no major problem, combined it throws you into a dependency hell for days hunting for dependencies that work.
Hope they resolve this issue. People promised a solution in the blog comments, then promised a solution a year later as the issue surfaced again on the #typesafe blog.
http://codemonkeyism.com/scala-unfit-development/
There are two forces at play here:
a.) Binary fragility of Scala
b.) A community that upgrades libraries (your dependencies) to every new RC candidate - even when only fixing bugs. So if you have a show stopper bug you need to upgrade to the newest RC breaking all your other dependencies.
Either a. and b. would be no major problem, combined it throws you into a dependency hell for days hunting for dependencies that work.
Hope they resolve this issue. People promised a solution in the blog comments, then promised a solution a year later as the issue surfaced again on the #typesafe blog.