+201223538180

neoweb4u|Web site Developer I Advertising I Social Media Advertising I Content material Creators I Branding Creators I Administration I System Resolution|KotlinConf 2019: What's New in Java 19: The tip of Kotlin? by Jake Wharton

neoweb4u|Web site Developer I Advertising I Social Media Advertising I Content material Creators I Branding Creators I Administration I System Resolution|KotlinConf 2019: What's New in Java 19: The tip of Kotlin? by Jake Wharton

Neoweb4u


Neoweb4u|Recording delivered to you by American Specific. https://americanexpress.io/kotlin-jobs Kotlin’s introduction was a breath of recent air at a time when the tempo of …

supply

46 thoughts on “neoweb4u|Web site Developer I Advertising I Social Media Advertising I Content material Creators I Branding Creators I Administration I System Resolution|KotlinConf 2019: What's New in Java 19: The tip of Kotlin? by Jake Wharton

  1. Java is one of the worst languages in the world. Thank god for allowing us to use Kotlin 🙏

  2. Very nice balanced and informative presentation.

  3. If it wasnt for android and google's pressure on developers, kotlin would not even had a chance even to end.

  4. why is this guy talking about JAVAsyntax as if Kotlin was the first one to do ALL of the features?

  5. … so when is Java getting extension methods/properties and inline/reified methods???

  6. End of kotlin? wtf lol, i love kotlin more than java.

  7. Not even 1 minute in and he started trolling Go. How serious should I take this talk…

  8. Optional<T> is the way Java introduced to deal with null safety. It's not a language feature, but you can use it anyway, if you need to. It's used by popular frame works as JPA.

  9. but java forced you to do everything in OOP which is sucks..no thank you

  10. During the whole video I was thinking: but Java won't have nullability! And yes, in the end Jake said it.
    Just because of nullability Kotlin will remain much more convenient and efficient, than Java

  11. Release 19, Java still has no string interpolation? No need to watch the rest of the video — DISLIKE

  12. C# смотрит на обоих с ухмылкой…

  13. Literally came here from introduction to kotlin vedio feeling very stupid.

  14. Kotlin is a bless to all developers

  15. Java 15 September 2020, so accurate!

  16. I think what kotlin and java ecosystem lacks are a more standard toolchains. In go and rust world, I don't have to fight the toolings and choose which code standard that I wanted to choose. If only in kotlin I can just generate "kotlin init my-project" with all the minimal best practices, and no linter settings, just make it standard toolins. And if I could do "kotlin run" or "kotlin build", I think it will catchup to more developers.

  17. That positional destructuring is pretty gross.

  18. I very much enjoyed this talk. Clear, considered and unbiased comparison. Nice one.

  19. Why is the java code missing the pesky semicolons that java requires but kotlin does not? Did I miss a massive upgrade to java that eliminates the need for semicolons everywhere?

  20. What does he mean with "Kotlin has an IDE to potentially evolve in ways that Java cannot" (48:14)? IntelliJ also supports Java.

  21. I'm still at java 8. Tried migrating to java 9, whole project crashed. Went back to java 8 🤣

  22. Great Content keep it up bro!

  23. Java died already long ago, since the time Oracle took over (greed); Java is the walking dead.

  24. When you actually have to write and maintain real code for a living you don't want rapid change.

  25. should I be worried if I am still learning java 8?

  26. Why the fuck both Java and Kotlin destructure objects based on field ordering, not by their names? This is insane. Destructure by property names, like Javascript does, and then it doesn't break when you add new fields. E.g. val {age, name} = person that will fail if person does not have properties named name and age but doesn't care about their order or whether there are also other properties.

  27. I wonder why all languages are still so much struggling with multi-line string literals. It should be obvious that whitespace needs to be automatically removed from both ends of each line. With languages using """ the indent width can be determined from the final line from the sequence of tabs and spaces that comes before the closing quote (and make it a syntax error if other lines do not include that sequence in their beginning). Languages using indented string blocks with no closing quotes (like YAML) have a bit harder time because extra markup to mark the margin is often required and that is just ugly. Such languages should probably mandate an indent width of two spaces for the whole language, and then (a) the string continues as long as each (non-empty) line has at least two spaces more than the line prior to the string block, and (b) omit the prior indent plus two spaces from string content (any more indent than that becomes string content).

  28. Java. The shittiest language on the JVM

  29. Weak. Just learn Java. Stop splitting the JVM community over syntactic sugar.

    Kotlin is a fad. Just like Scala.
    Until Java 19, you can use libraries like Lombok and Vavr and achieve so much.

  30. A clickbaiter admitting this is a clickbait. That's a first.

  31. Here's how you get the fancy not equal to operator: https://stackoverflow.com/q/41774046

  32. Dont talk shit man, i just moved to kotlin!

  33. Java (rabbit) will never catch Kotlin (turtle). Because Kotlin introduced improvements to Java, right? When Java catch up with those improvements, Kotlin will be more advanced in the meantime. And again, and again.
    That's why Kotlin will always be more advanced than Java. Got it?
    😜

  34. So both Kotlin and Java will continue to take in features that Scala already has right now, but at a rather slow pace.

  35. Your daily reminder that you could do all this in LISP in 1958.

  36. Oracles newest license changes will kill jvm languages long before 2022. .Net Core is going to eat our lunch.

  37. The only Java version numbers that truly matter though are the LTS (Long Term Support) versions. So, Java 11, right now.

  38. Java is still alive I thought it died a while ago

  39. Variable Type Inference (Java 10) [3:59]
    Local Functions (Java 16/17) [7:15]
    Multiline Strings (Java 15) [10:38]
    Value-Based Classes (Java 15/16 Records) [18:20]
    Sealed Hierarchies (Java 15/16) [22:40]
    Type Matching (Java 15/16) [25:56]
    Destructuring [29:09]
    Coroutines [45:07]
    Executores.networkStealingPool()
    The end of Kotlin? [46:40]
    Java 16/17 Pattern Matching
    Java 14: Expression Switch
    Java 18/19: Inline Classes
    Java 16/17: Virtual Threads
    conclusion [47:21]

  40. The internet manual, rule 47:
    -Any youtube video phrased as a question can be answered with a simple NO

  41. TLDR; The answer is no

  42. I've just finished a book about Java 1.0.2

Leave a Reply