Announcement

Collapse
No announcement yet.

Chrome 72 Poised To Have Some Wayland Performance Improvements

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

  • #11
    The "KDE stuff" are not ready yet. There are a lot of issues still.

    Comment


    • #12
      Originally posted by TemplarGR View Post
      The "KDE stuff" are not ready yet. There are a lot of issues still.
      developers are not able?

      Comment


      • #13
        Kde wayland is still very young

        Comment


        • #14
          Originally posted by nanonyme View Post
          I wasn't entirely convinced in Chromium code review efficiency when I was observing how Wayland commits were being integrated to their codebase. It was like leaving contributors waiting for weeks or months for feedback
          Were the contributions from Google employees, or outsiders?

          Comment


          • #15
            Can the top two browsers please put more effort into native wayland already? I'll be wearing diapers by the time it's ready.

            Comment


            • #16
              Originally posted by brrrrttttt View Post
              Were the contributions from Google employees, or outsiders?
              afaik most of the chrome wayland work has been done by intel and igalia

              Comment


              • #17
                Originally posted by brrrrttttt View Post
                Were the contributions from Google employees, or outsiders?
                Igalia, so externals. On one component mandatory for Wayland track there was submission hanging like half a year. Seems to me Chromium project has exactly same lack of maintainers issue that was just reported on Weston

                Comment


                • #18
                  GPu memory buffering support! IT's amazing!

                  Comment

                  Working...
                  X