4 ms·
> you lose all the type conversions between Java arrays and Scala arrays This is what killed scala to me. It talks up a big story about Java interop, but the r
by zmmmmm 7y ago
> you lose all the type conversions between Java arrays and Scala arrays
This is what killed scala to me. It talks up a big story about Java interop, but the reality is that the separate collections really drive a wedge between the scala ecosystem and the rest of the JVM world so it does not have the kind of seamless iterop that Kotlin and (especially) Groovy do.
- dwohnitmok 7y agoI have my share of grievances against Scala, but the difference in collection libraries only feels painful if your app can't tolerate the performance hit of re-copying a collection (which to be fair does sometimes occur on hot codepaths). Otherwise it's a simple .toScala or .toJava call away. Also arrays are one place where Scala and Java do happen to share the same collection.
- pjmlp 7y agoA good example of why platform languages always reign on their turf.