To Java 21 and Beyond! by Billy Korando @ Spring I/O 2023

Поделиться
HTML-код
  • Опубликовано: 28 авг 2024
  • Spring I/O 2023 - Barcelona, 18-19 May
    Slides: wkorando.githu...
    Java 17 has come and gone, but development on Java continues on! What has changed since Java 11? And what changes are being added in Java 21? Come find out!
    In this presentation we will look at the key changes that have been added to Java post-8, focusing primarily on Java post-11. The large changes; the Module System and Records, quality of life improvements; var, text blocks, pattern matching, and the many performance and runtime improvements. A lot has changed in the JDK in recent releases, take this opportunity to get caught up!

Комментарии • 9

  • @1dayitwillmake763
    @1dayitwillmake763 Год назад +1

    Great talk!

  • @yeshengwei79
    @yeshengwei79 8 месяцев назад

    I have already added Virtual Threads and Structured Concurrency in my e-Commerce Big Data Analysis project. During the development, I found that it will be a plus if Java Structured Concurrency supports scopes within a scope (namely, to fork children subtasks of a parent subtask). Does Oracle have a plan to implement such a feature in the future?

  • @shakilahmed4647
    @shakilahmed4647 Год назад

    Do you guys realize how much you're copying kotlin?

    • @VikasAdiwal
      @VikasAdiwal Год назад +5

      If a feature is helpful it should be shared across. Kotlin also takes alot from a number of languages. No point in shaming a language for adding features. Everyone copies everyone

    • @billykorando6820
      @billykorando6820 Год назад +5

      To add to what @vikasadiwal said. Part of our strategy with Java is to learn from what other languages are doing and incorporate popular and useful features into Java. What Brian Goetz refers to as “Java’s last mover advantage”.
      So yes, we realize we are “copying” language features from Kotlin, and other languages, that’s part our strategy of language stewardship.

    • @piyalAhmed
      @piyalAhmed 11 месяцев назад

      Doing something better is to copy existing thing then add some more features or optimize it.

    • @shakilahmed4647
      @shakilahmed4647 11 месяцев назад

      to avoid any further arguments - I wasn't criticising or anything, just thought it looks lot similar to kotlin, thats it.

  • @Anbu_Sampath
    @Anbu_Sampath Год назад +1

    @18.15 when should be "when @mName.isEmpty()"