80% of Java features in the last few years are Scala features with worse syntax, because the better syntax would not be backwards compatible. It's not good for Scala 3 adoption in industry , but I would argue Martin has no interest whatsoever helping that. He's happy with his research language that somehow has enough good features some companies put it in prod. Languages that care about industrial usage just organize themselves differently.
No affiliation with either, but I don't think Java and Scala are punching at each other, and they're both doing great. Needless to say Java has continued to exceed expectations and given its huge role in the world, that's worth [handwave very huge number] in consumer welfare. Scala has evolved the last several years to again become perhaps the most interesting big-ish application language, eg see Odersky's recent https://scaladays.org/session/opening-session-keynote/ and https://dl.acm.org/doi/10.1145/3786335.3813127
I like a lot of Scala but dislike implicits. I feel like it is the wrong abstraction in that it is similar to implicit type conversion in C/C++, making it harder to reason about what the code is doing and navigating to the types/methods being called.
I prefer extension methods for what Scala implicits do [1], [2]. The only part that is lacking with extension methods is to be able to extend a type to implement an interface, e.g. Comparable, but you can create extension methods that return anonymous objects [3].
80% of Java features in the last few years are Scala features with worse syntax, because the better syntax would not be backwards compatible. It's not good for Scala 3 adoption in industry , but I would argue Martin has no interest whatsoever helping that. He's happy with his research language that somehow has enough good features some companies put it in prod. Languages that care about industrial usage just organize themselves differently.
No affiliation with either, but I don't think Java and Scala are punching at each other, and they're both doing great. Needless to say Java has continued to exceed expectations and given its huge role in the world, that's worth [handwave very huge number] in consumer welfare. Scala has evolved the last several years to again become perhaps the most interesting big-ish application language, eg see Odersky's recent https://scaladays.org/session/opening-session-keynote/ and https://dl.acm.org/doi/10.1145/3786335.3813127
I still write Scala. But not sure for how long. I swear, it's such a joy to write code in Scala.
It's like French poetry.. So much elegance. An no effect system BS. Just like Martin Odersky intended it to be!
I like a lot of Scala but dislike implicits. I feel like it is the wrong abstraction in that it is similar to implicit type conversion in C/C++, making it harder to reason about what the code is doing and navigating to the types/methods being called.
I prefer extension methods for what Scala implicits do [1], [2]. The only part that is lacking with extension methods is to be able to extend a type to implement an interface, e.g. Comparable, but you can create extension methods that return anonymous objects [3].
[1] https://kotlinlang.org/docs/extensions.html#anonymous-extens...
[2] https://learn.microsoft.com/en-us/dotnet/csharp/programming-...
[3] https://discuss.kotlinlang.org/t/extensions-function-to-impl...
>it's such a joy to write code in Scala.
Yes, but also a bit of a torture to read code in it..
Agree. Really enjoy it—without type effects libs.
Curious what you meant about the effect system BS?
I'm assuming they mean Scala doesn't have the tortured Haskell IO monad.
3 replies →
Sigh, I so very miss writing Scala.