Announcement

Collapse
No announcement yet.

OpenJDK Java's Native Wayland Support Progressing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • OpenJDK Java's Native Wayland Support Progressing

    Phoronix: OpenJDK Java's Native Wayland Support Progressing

    OpenJDK/Java has been making progress on implementing native "pure" Wayland toolkit integration not dependent upon X.Org/X11 or XWayland for rendering of Java GUI applications...

    https://www.phoronix.com/news/Java-N...yland-Progress

  • #2
    Typo:

    Originally posted by phoronix View Post
    Java's Wakefield repository wit hthe "pure_wl_toolkit" branch.

    Comment


    • #3
      Does anyone know why they implement it from scratch and don't use libraries like wlroots?!

      Comment


      • #4
        Originally posted by Steffo View Post
        Does anyone know why they implement it from scratch and don't use libraries like wlroots?!
        Because wlroots is for building compositors. They're not building a compositor, but a support for gui Java apps. Think of it as a competition to Qt and GTK.

        Comment


        • #5
          Originally posted by Steffo View Post
          Does anyone know why they implement it from scratch and don't use libraries like wlroots?!
          wlroots is for server side, for compositor. This article is about application support

          Comment


          • #6
            Originally posted by slagiewka View Post

            Because wlroots is for building compositors. They're not building a compositor, but a support for gui Java apps. Think of it as a competition to Qt and GTK.
            Right, thx.

            Comment


            • #7
              Originally posted by Steffo View Post
              Does anyone know why they implement it from scratch and don't use libraries like wlroots?!
              As others have mentioned, wlroots is for the server. The better question is why they don't base it on GTK (or Qt). That way, Java applications wouldn't stand out like a sore thumb everywhere.

              Comment


              • #8
                Shhh... what's that sound? The sound of change. Client side java wave. (hey, it could happen...)

                Comment


                • #9
                  That image, it's like something out of the early 2000's...

                  Actually scrap that, the late 90's.

                  Comment


                  • #10
                    Originally posted by cjcox View Post
                    Shhh... what's that sound? The sound of change. Client side java wave. (hey, it could happen...)
                    Only morons use Java on the client side. Competent programmers learnt it the hard way. VM startup takes forever. GC absolutely kills the performance. Toolkits look ancient. Applets are a joke. Oh applet support is actually deprecated in all modern browsers.

                    If you want to use a dynamic client side language, Python 2 or 3 would be the best. Ref counting has much better interactive performance. Qt bindings also look decent and the Qt company provides excellent open source support for free. Qt has much better performance. Also each Kde release has lots of Wayland fixes, which helps Qt.

                    Comment

                    Working...
                    X