No announcement yet.

Louvre Is A New C++ Library Helping To Build Wayland Compositors

  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Originally posted by user1 View Post

    If you mean the bad choice was the overly minimalistic design of the Wayland protocol, I agree, but..

    You don't seem to realize that there will never be a standard Wayland implementation / display server. That just never going to happen. Big projects like Gnome and KDE already have their own Wayland display server implementations, so I just don't see them scrapping years of work that has been put into Mutter and KWin Wayland support in favor of some mythical "standard" Wayland display server.
    Never say never. GNOME and KDE were both heavily invested in their ORBit and DCOP IPC systems and happily threw them out when DBUS came along. They had their own audio servers and moved to Pulse Audio (and now PipeWire). They had their own session management logic and readily switched to systemd (at least GNOME did, not sure about KDE). So if there was a Wayland display manager foundation that does what they need, I don't see why they would eventually use it if ultimately it allows them to reduce their development effort.


    • #32
      Is there a library to simplify creating a wayland *client*? All the fuss seems to be around compositors.


      • #33
        Originally posted by JMB9 View Post

        Well, so Linux is written in ... ups, C ... is there any OS currently being technically superior to Linux?
        And all the effort concerning Rust is done to get a few drivers wirtten by ... a larger group of people ...
        which lead to usage of Java (and formerly BASIC) ...

        So looking at currently used code in important cases we see basically C, Cobol, Fortran ...
        and after a gap a huge croud of programming languages (of more than 2000 if countable at all;
        see "The Mess We're In" by Joe Armstrong:
        But maybe someone could shed some light about programming language usage who really knows better.
        And a lot of code is used behind closed doors ...

        Personally, I like having C++ libraries for all purposes - as after my taste C++ would (after C and Fortran
        used in former times) be most attractive (games, GUIs, ...) - while Rust is really in its infancy and
        moving quite fast. But Linux may be a reason that it will get ripe sooner than later ... we will see.

        I think that every technical task without at least 2 alternatives is a problem.
        Would anyone be happy if only GNOME would exits? Choice is important for experts.
        Only beginner are happy to not have any choice or not having plenty of options - as
        experts have to tailor everything to their needs to work in the most effective way
        possible (i.e. {nearly} no mouse or touch screen).


        • #34
          Originally posted by uid313 View Post
          But can it do gamma correction, Night Light, HDR, ICC color profiles, and v-sync?
          chill out, it's a new library


          • #35
            Originally posted by kpedersen View Post

            By the time they do standardize; wlroots probably won't even exist or be used anymore. Plus things like Weston and Sway will be seen as the old TWM of Wayland compositors.
            i don't like the standardize on wlroots, they have a lot of extensions that are outside of the official wayland protocol, it's like xorg, that implement so much things outside of the x11 protocol, maybe with 2 or 3 big compositors this can be fixed, so devs target the official extensions and it work on everything


            • #36
              Originally posted by Brittle2 View Post

              i don't like the standardize on wlroots, they have a lot of extensions that are outside of the official wayland protocol
              I get that. It seems to act like a polyfill whilst Wayland matures and people start to notice all the stuff they actually need.


              • #37
                Originally posted by juxuanu View Post
                Is there a library to simplify creating a wayland *client*? All the fuss seems to be around compositors.


                • #38
                  Originally posted by Morty View Post

                  That does much more than what I asked for.


                  • #39
                    Originally posted by zexelon View Post
                    Lets be honest... fragmentation IS the number one product of the Linux ecosystem.
                    I have several different overlapping and/or contradictory opinions about that ;-)


                    • #40

                      Originally posted by mmstick View Post

                      Probably because they wanted to write a Wayland compositor natively in C++ rather than C. Same as why Smithay exists as a Wayland compositor library for Rust.
                      Yeah that's probably that.​

                      Originally posted by Kemosabe View Post

                      One of the reasons may be: C is simply not suitable for the 21st century anymore.
                      Isn't that the same for C++?

                      Originally posted by ehansin View Post

                      Well, neither are written in Rust, so there is that problem (relax, relax, just making a funny!)

                      But for real, I sort of see two somewhat contradictory, yet both valid takes in the whole open source thing:

                      * Too much duplicated effort across similar projects trying to scratch the same itch.
                      * People exploring different pathways to solve similar problems can come across new ideas that might not reveal themselves if there was not this duplicated effort.

                      I don't think there is a singular one right answer to the above, both are valid takes. I suppose it is like a lot of things in life, answer sort of falls somewhere in the middle or can be both at the same time. When does energy and efforts become so dispersed to the point of absurdity, and when are efforts so concentrated that it leads to group-think and tunnel vision?
                      Yeah I feel you, but there's already plenty of non-wl-root compositors, not sure we needed more; of course, maybe those compositors will eventually migrate to this because it could end up better or more appropriate language or something else.