[frowaway001]

> It's more a question of do you want to spend engineering hours updating all your tools to the latest version, or do you want to spend engineering hours developing features.

How is this different from e. g. Java? Developers pick a version which works for them and stick with it until it makes business sense to upgrade.

> In most cases I'd rather not use technology that is continually breaking my code on every update, and instead focus on solving interesting domain specific problems.

How is this the case for Scala?

[kasey_junk]

I've been developing Scala full time since 2.7. I have not had a release yet that didn't involve changing code to recompile to each new version.

I also have Java projects that were written in pre 1.0 releases that have updated to 1.7 without a single code change.

This is due to a different set of priorities. Each of those priorities has different costs and benefits but to act like Scala's lack of backwards compatibility doesn't have a cost is unfair.