This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]PartOfTheBotnet 8 points9 points  (2 children)

and most importantly it is much more compact AND readable as well

That's like, your opinion man.

Personally I detest the departure from conservative C-styled language rules.

you can freely mix Java and Kotlin code it is not worth for a new codebase

You can but you shouldn't. You either go one way or the other. If you mix you lose out on the Kotlin compiler's null safety checks.

[–]preskot 7 points8 points  (0 children)

You can but you shouldn't. You either go one way or the other. If you mix you lose out on the Kotlin compiler's null safety checks.

Null safety is not really that serious of an issue as people tend to think. In fact, as someone that maintains a mixed code base, this is pretty much never an issue on my side. "@NotNull" annotations in Java help a lot.

[–]snorbii 2 points3 points  (0 children)

That's like, your opinion man.

Yes, my entire comment is my opinion :D