4 ms·

If a new language feature is available, someone in your team will start to use it, because it compiles, and code becomes shorter, so why not. And you will have

If a new language feature is available, someone in your team will start to use it, because it compiles, and code becomes shorter, so why not. And you will have to review their code daily, which forces to "relearn" the language. I think this is why OP complains.

nradov 8y ago
What's wrong with relearning the language? That's nothing new for developers.
- bitL 8y ago
  Why wouldn't you rather learn a new one if your old one is changing rapidly into a weaker version of some other language that did it better already? I personally don't care at all about those new things; I have them in Scala, I don't need them in Java. I can mix those two as I like anyway. I'd much rather see type erasure fixed, as that messes up every single language based on JVM. But that would be like "the incompatible change" of a decade...
  - virtualwhys 8y ago
    > I'd much rather see type erasure fixed, as that messes up every single language based on JVM What? Type erasure is one of the main reasons why the JVM is targeted by so many languages (Java, Clojure, Kotlin, Scala, Groovy, JRuby, etc.). Had the JVM gone the way of the CLR the programming language landscape would probably look a lot different than it does today. Perhaps you mean lack of support for value types? That does affect every language running on the JVM.
    - xg15 8y ago
      > Type erasure is one of the main reasons why the JVM is targeted by so many languages. As someone who grapples with erasure as well, I haven't heard this argument before. Could you explain that?
rossjudson 8y ago
You're not already reviewing their code and gating change? I think you should start there. Learning from other peoples' code is not generally considered harmful.