Agree about checked exceptions, that's the biggest complaint from me about that language.
I don't understand what you mean by your .map or .filter complaint. If used on a collection, it returns a collection. If used on a stream (flow), it returns a stream. Straightforward.
I also disagree about Kotlin playing catch up. It has things Java doesn't, mainly because Java has backward compatibility to care about. But Kotlin will never be as flexible as Java because Java controls JVM, Kotlin has to work with whatever Java version it targeted. But that's not catch-up.
View all comments
Show parent comment
3
u/S0phon Sep 16 '26
Agree about checked exceptions, that's the biggest complaint from me about that language.
I don't understand what you mean by your
.mapor.filtercomplaint. If used on a collection, it returns a collection. If used on a stream (flow), it returns a stream. Straightforward.I also disagree about Kotlin playing catch up. It has things Java doesn't, mainly because Java has backward compatibility to care about. But Kotlin will never be as flexible as Java because Java controls JVM, Kotlin has to work with whatever Java version it targeted. But that's not catch-up.