Great video! Under the heading of "more functional" I do wish Urs had mentioned the fact that many more things are expressions in Kotlin than in Java. For example, try, if, and when among others all return a value. This eliminates the all-too-common and error prone pattern of creating a local variable initialized to null upstream of a block, and then assigning to it inside a conditionally-executed block. Instead, the if/else or try/catch itself returns a value. This contributes to concision, safety, and readability.
It's not correct to say there is no parallelism in virtual thread. There is virtualThreadPerTaskExecutor and structured concurrency support (which is in preview, but haven't changed much) to execute things concurrently. On JVM, you forgot about other major advantages of using virtual threads like better debugging , stack trace, profiling etc.
I dont understand the trend to make comparison amogn these two languages. Man can make safe and readable code in java & kotlin. All features are now available in both languages, it only differs in what it is called and the usage (for example extension functions you replace with util classes or use bytecode maven plugin for support it dirrectly). This comparision sessions are only for guys liking the smell of their farts (south park if you know :D)
Great video! Under the heading of "more functional" I do wish Urs had mentioned the fact that many more things are expressions in Kotlin than in Java. For example, try, if, and when among others all return a value. This eliminates the all-too-common and error prone pattern of creating a local variable initialized to null upstream of a block, and then assigning to it inside a conditionally-executed block. Instead, the if/else or try/catch itself returns a value. This contributes to concision, safety, and readability.
It's not correct to say there is no parallelism in virtual thread. There is virtualThreadPerTaskExecutor and structured concurrency support (which is in preview, but haven't changed much) to execute things concurrently. On JVM, you forgot about other major advantages of using virtual threads like better debugging , stack trace, profiling etc.
Concurrency and Parallelism are not the same thing.
Gain! Unfortunatelly Kotlin for backend doesn't get enough
Nice video, Happy Kotliner
14:57 Java records now supports derived records (JEP 468)
Truly excellent talk highlighting the many benefits of Kotlin. Thanks for also going into WebFlux and coroutines towards the end.
15:51 using kotlin data classes as JPA entites is not a good idea.
Yes he mentioned that specifically.
Is there any way to call suspend function from a non suspend function? Does it even make sense?
Not directly. You have to use something like runBlocking
the only thing i absolutely hate about java is the lack of async await
reactive programming is not nice to work with in java reactor
Kotlin's syntax and concepts are similar with C#, which one comes first😃
Kotlin is much more ergonomic and concise. Over the period of time, C# has become a kitchen sink language.
Kotlins come and go. Java stays forever 😊
Naaa. With the way companies are adopting Kotlin, Kotlin seems to be the future; obviously in Mobile apps , KMM and Server-side.
Someone said that Kotlin is valuable just because it doesn't use semicolons.
Null to optional 😂 good point that’s a total anti pattern for optional
I dont understand the trend to make comparison amogn these two languages. Man can make safe and readable code in java & kotlin. All features are now available in both languages, it only differs in what it is called and the usage (for example extension functions you replace with util classes or use bytecode maven plugin for support it dirrectly). This comparision sessions are only for guys liking the smell of their farts (south park if you know :D)
Scala cult, Groovy cult, amd now Kotlin cult
and yet Google ditched the Java cult