> - it [getting Scala to work with Java] can be verbose sometimes
Fixed. You're reading that sentence wrong. It's still supporting the author's point. Also, it's not easy to learn [just because you're coming from Java]... This also supports his point that's it's better to treat Scala as a new language than as Java++. I grant you the IDE and the backward compatibility points, but those speak more to it's immaturity than it's "intrinsic superiority".
Having said all that, I agree that it might take Scala a long while to compete with Java. And I think the main reason for that is that it's hard. It's a bit too elegant, if you know what I mean. The syntax ends up being too sugary and consequently looks mystifyingly clever at times. I can think about OOP reasonably well, and I can do FP reasonably well, but personally it still takes my mind a while to wrap both those together. And that's the main reason I'm really into Scala right now, I find it incredibly challenging. I think as Scala comes more into production we'll see the development of more pedestrian idioms that can be easily absorbed by the industrial programmers.
I grant you the IDE and the backward compatibility points, but those speak more to it's immaturity than it's "intrinsic superiority".
Scala is ten years old, the fact that it's still immature in these areas is a concern. If this hasn't been addressed in ten years of existence, it seems unlikely it ever will.
Comments
Fixed. You're reading that sentence wrong. It's still supporting the author's point. Also, it's not easy to learn [just because you're coming from Java]... This also supports his point that's it's better to treat Scala as a new language than as Java++. I grant you the IDE and the backward compatibility points, but those speak more to it's immaturity than it's "intrinsic superiority".
Having said all that, I agree that it might take Scala a long while to compete with Java. And I think the main reason for that is that it's hard. It's a bit too elegant, if you know what I mean. The syntax ends up being too sugary and consequently looks mystifyingly clever at times. I can think about OOP reasonably well, and I can do FP reasonably well, but personally it still takes my mind a while to wrap both those together. And that's the main reason I'm really into Scala right now, I find it incredibly challenging. I think as Scala comes more into production we'll see the development of more pedestrian idioms that can be easily absorbed by the industrial programmers.
Thanks for the correction.
Scala is ten years old, the fact that it's still immature in these areas is a concern. If this hasn't been addressed in ten years of existence, it seems unlikely it ever will.