News for hackers. Stuff that matters.

A comment on Scala Native. Parent comment

Re:Scala Native by zmmmmm on Monday August 19, 2019 @10:23PM (#20743353)
> 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.

[ Parent | on HN ]
Re:Scala Native by dwohnitmok on Tuesday August 20, 2019 @12:22AM (#20743812)
I 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.

[ Parent | on HN ]
Re:Scala Native by pjmlp on Tuesday August 20, 2019 @05:35AM (#20745107)
A good example of why platform languages always reign on their turf.
[ Parent | on HN ]