@wfaler @channingwalton But it's been such a long time since it was last necessary! It's the tradeoff between progress and stability...
-
-
Replying to @propensive
@wfaler@channingwalton Anyway, the problem isn't limited to new Scala releases. It applies to any dependency.1 reply 0 retweets 0 likes -
Replying to @propensive
@propensive@wfaler I’m actually happy that scala is doing this, rather this than Java-like stagnation3 replies 0 retweets 2 likes -
Replying to @channingwalton
@channingwalton@propensive@wfaler false dichotomy, though.1 reply 0 retweets 0 likes -
Replying to @puffnfresh
@puffnfresh@propensive@wfaler perhaps. Am I wrong to think that being prepared to break compatibility enables the language to develop?2 replies 0 retweets 0 likes -
Replying to @channingwalton
@channingwalton@propensive@wfaler maybe but I think compatibility should be a library dependency concern, not a language one.2 replies 0 retweets 0 likes
@puffnfresh @channingwalton @wfaler That might depend on your starting point...
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.