home.social

#jdk21 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #jdk21, aggregated by home.social.

  1. 100k blocking tasks. A few seconds. On a laptop. With #VirtualThreads in #Java25, that’s reality. Mihaela Gheorghe-Roman explains what changed since #JDK21 & why thread-per-request is back. Still running huge thread pools?

    Rethink: javapro.io/2026/03/05/java-25-

    #ProjectLoom @openjdk

  2. 100k blocking tasks. A few seconds. On a laptop. With #VirtualThreads in #Java25, that’s reality. Mihaela Gheorghe-Roman explains what changed since #JDK21 & why thread-per-request is back. Still running huge thread pools?

    Rethink: javapro.io/2026/03/05/java-25-

    #ProjectLoom @openjdk

  3. 100k blocking tasks. A few seconds. On a laptop. With #VirtualThreads in #Java25, that’s reality. Mihaela Gheorghe-Roman explains what changed since #JDK21 & why thread-per-request is back. Still running huge thread pools?

    Rethink: javapro.io/2026/03/05/java-25-

    #ProjectLoom @openjdk

  4. 100k blocking tasks. A few seconds. On a laptop. With #VirtualThreads in #Java25, that’s reality. Mihaela Gheorghe-Roman explains what changed since #JDK21 & why thread-per-request is back. Still running huge thread pools?

    Rethink: javapro.io/2026/03/05/java-25-

    #ProjectLoom @openjdk

  5. 🚀 Call for Contributors – #JVM #Performance #Benchmarks

    If you're interested in contributing to the #JVM #Performance #Benchmarks project - an initiative that gained significant traction in the #Java community through our recent #JDK17 and #JDK21 analyses - check out the repo:

    🔗 github.com/ionutbalosin/jvm-pe

    🧵 DM me or open a PR to get started

    #Java #JVM #OpenJDK #GraalVM #JMH #Performance #OpenSource

  6. 🚀 Call for Contributors – #JVM #Performance #Benchmarks

    If you're interested in contributing to the #JVM #Performance #Benchmarks project - an initiative that gained significant traction in the #Java community through our recent #JDK17 and #JDK21 analyses - check out the repo:

    🔗 github.com/ionutbalosin/jvm-pe

    🧵 DM me or open a PR to get started

    #Java #JVM #OpenJDK #GraalVM #JMH #Performance #OpenSource

  7. 🚀 Call for Contributors – #JVM #Performance #Benchmarks

    If you're interested in contributing to the #JVM #Performance #Benchmarks project - an initiative that gained significant traction in the #Java community through our recent #JDK17 and #JDK21 analyses - check out the repo:

    🔗 github.com/ionutbalosin/jvm-pe

    🧵 DM me or open a PR to get started

    #Java #JVM #OpenJDK #GraalVM #JMH #Performance #OpenSource

  8. 🚀 Call for Contributors – #JVM #Performance #Benchmarks

    If you're interested in contributing to the #JVM #Performance #Benchmarks project - an initiative that gained significant traction in the #Java community through our recent #JDK17 and #JDK21 analyses - check out the repo:

    🔗 github.com/ionutbalosin/jvm-pe

    🧵 DM me or open a PR to get started

    #Java #JVM #OpenJDK #GraalVM #JMH #Performance #OpenSource

  9. 🚀 Call for Contributors – #JVM #Performance #Benchmarks

    If you're interested in contributing to the #JVM #Performance #Benchmarks project - an initiative that gained significant traction in the #Java community through our recent #JDK17 and #JDK21 analyses - check out the repo:

    🔗 github.com/ionutbalosin/jvm-pe

    🧵 DM me or open a PR to get started

    #Java #JVM #OpenJDK #GraalVM #JMH #Performance #OpenSource

  10. @svenruppert In #JabRef, we stick with #JDK21, because the new features of JDK22 do not outweigh the updates the effort of Linux distributions packaging our app with a more recent #JDK. Regarding #JavaFX, we always go with the latest release - and also build with the latest EA version to enable testing by Linux users whether their bugs (mostly with Gnome and i3) are fixed. Our #GitHub #workflow is github.com/JabRef/jabref/blob/.

  11. @svenruppert In #JabRef, we stick with #JDK21, because the new features of JDK22 do not outweigh the updates the effort of Linux distributions packaging our app with a more recent #JDK. Regarding #JavaFX, we always go with the latest release - and also build with the latest EA version to enable testing by Linux users whether their bugs (mostly with Gnome and i3) are fixed. Our #GitHub #workflow is github.com/JabRef/jabref/blob/.

  12. @svenruppert In #JabRef, we stick with #JDK21, because the new features of JDK22 do not outweigh the updates the effort of Linux distributions packaging our app with a more recent #JDK. Regarding #JavaFX, we always go with the latest release - and also build with the latest EA version to enable testing by Linux users whether their bugs (mostly with Gnome and i3) are fixed. Our #GitHub #workflow is github.com/JabRef/jabref/blob/.

  13. Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: bit.ly/4cEppIA

    This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.

    This analysis guides Java developers on when and how to use virtual threads in their applications.

    #JDK21 #VirtualThreads #OpenLiberty

  14. Dive into the latest advancements in with our latest article on JDK 21's virtual threads: bit.ly/4cEppIA

    This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.

    This analysis guides Java developers on when and how to use virtual threads in their applications.

  15. Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: bit.ly/4cEppIA

    This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.

    This analysis guides Java developers on when and how to use virtual threads in their applications.

    #JDK21 #VirtualThreads #OpenLiberty

  16. Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: bit.ly/4cEppIA

    This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.

    This analysis guides Java developers on when and how to use virtual threads in their applications.

    #JDK21 #VirtualThreads #OpenLiberty

  17. Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: bit.ly/4cEppIA

    This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.

    This analysis guides Java developers on when and how to use virtual threads in their applications.

    #JDK21 #VirtualThreads #OpenLiberty

  18. avis partagé !! RT @AlexisHassler Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère. #jdk #jdk21 #VirtualThreads

  19. avis partagé !! RT @AlexisHassler Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère. #jdk #jdk21 #VirtualThreads

  20. avis partagé !! RT @AlexisHassler Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère. #jdk #jdk21 #VirtualThreads

  21. avis partagé !! RT @AlexisHassler Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère. #jdk #jdk21 #VirtualThreads

  22. Il n'apparaissent pas avec jstack, jconsole ou visualvm.
    Avec jcmd, on les voit avec la commande Thread.dump_to_file, mais pas avec Thread.print 🤯.
    #jdk #jdk21 #VirtualThreads

  23. Il n'apparaissent pas avec jstack, jconsole ou visualvm.
    Avec jcmd, on les voit avec la commande Thread.dump_to_file, mais pas avec Thread.print 🤯.
    #jdk #jdk21 #VirtualThreads

  24. Il n'apparaissent pas avec jstack, jconsole ou visualvm.
    Avec jcmd, on les voit avec la commande Thread.dump_to_file, mais pas avec Thread.print 🤯.
    #jdk #jdk21 #VirtualThreads

  25. Il n'apparaissent pas avec jstack, jconsole ou visualvm.
    Avec jcmd, on les voit avec la commande Thread.dump_to_file, mais pas avec Thread.print 🤯.
    #jdk #jdk21 #VirtualThreads

  26. Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère.
    #jdk #jdk21 #VirtualThreads

  27. Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère.
    #jdk #jdk21 #VirtualThreads

  28. Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère.
    #jdk #jdk21 #VirtualThreads

  29. Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère.
    #jdk #jdk21 #VirtualThreads

  30. "JAVA IS HERE TO STAY!"

    #Java developers,

    Truly one of the most positive and upbeat Java articles I've encountered in a while. Have a read! Please AMPLIFY!
    💜☕️

    #JDK #JDK21 #Java21 #OpenJDK

    itpro.com/software/development