I’m curious how software can be created and evolve over time. I’m afraid that at some point, we’ll realize there are issues with the software we’re using that can only be remedied by massive changes or a complete rewrite.

Are there any instances of this happening? Where something is designed with a flaw that doesn’t get realized until much later, necessitating scrapping the whole thing and starting from scratch?

  • LeFantome@programming.dev
    1·
    9 months ago

    It is complex to build a Wayland compositor. When none existed, you had to build your own. So it took quite a while for even big projects like GNOME and KDE to work through it.

    At this stage, there are already options to build a compositor using a library where most of the hard stuff is done for you.

    https://github.com/swaywm/wlroots

    https://github.com/CuarzoSoftware/Louvre

    There will be more. It will not be long before creating Wayland compositors is easy, even for small projects.

    As more and more compositors appear, it will also become more common just to fork an existing compositor and innovate on top.

    One of the longer term benefits of the Wayland approach is that the truly ambitious projects have the freedom to take on more of the stack and innovate more completely. There will almost certainly be more innovation under Wayland.

    All of this ecosystem stuff takes time. We are getting there. Wayland will be the daily desktop for pretty much all Linux users ( by percentage ) by the end of this year. In terms of new and exciting stuff, things should be getting pretty interesting in the next two years.