driver733 / kotlin-vs-java Goto Github PK

Your project is very excellent. Especially the webpage with java and kotlin.But I find something is wrong with the code. As a newer,may be it's misleading.

For example:

Surely，You can do better for more honor.

Hi,
You've done a cool project!

Could you specify the version of two language. Maybe the codes should be re-organized by version in the future in order to avoid becoming obsolete.

For example, le chapter : Strings II
is true for java version < 13 but this feature (""" {formed String}""") is added in JAVA 13.

Regards

How about some coroutines? I don't think there's any other feature that makes Kotlin win by such a large margin as replacing a bunch of unwieldy, nested callbacks with clean sequential code.
Granted, it's not a one-liner example, but that is the problem with this kind of comparisons, the micro-scale differences in single-expression syntax aren't the things that make or break a language.

https://kotlinlang.org/docs/reference/multi-declarations.html

https://kotlinlang.org/docs/reference/coroutines/flow.html

The generics in the concurrency examples are interpreted as html tags and therefore don't show up.

java's list.sort() sorts this list, mutating it. kotlin's list.sortedBy() returns new list without mutating this

I don't think val x: Int would ever compile, to take an example from Variables I. It would have to be either lateinit or nullable.

It seems like the titles for the "Functions" tab do not really correspond to their code examples. For example:

fun hasItems() : Boolean {
    return true
}

has nothing to do with its title "Null I"

The Kotlin "Hello world" makes it kind of unclear how one can get command line arguments. Maybe have another "Hello, name" example that shows this?

At least to me, this site seems to be playing favorites to Kotlin over Java without declaring that anywhere (that I've found).

What I find off about this:

• The site is titled "Kotlin vs. Java", even though alphabetically J comes before K, suggesting a focus on Kotlin.
• The Java code in the Concurrency examples has obvious syntax errors.
• The Optional feature of Java is completely ignored in the nullability examples.
• Sometimes Lombock is used, sometimes it isn't, which either shows a lack of interest in consistency or in Java.
• The site doesn't show any scenarios where Kotlin is worse.
• The site also ignores the issues with calling Kotlin code from Java. And while the other way works much better, last I heard that there were still issues, especially when throwing annotation processing into the mix.

On the counterside, some examples do show Java in a better light, like Kotlin's removal of the tenary operator in favor of writing a full if else statement in one line.

I'm I wrong in thinking that this does not work in Java?

add ci