From the repo

Wayland Protocols has long had a problem with new protocols sitting for months, to years at a time for even basic functionality.

This is hugely problematic when some protocols implement very primitive and basic functionality such as frog-fifo-v1, which is needed for VSync to not cause GPU starvation under Wayland and also fix the dreaded application freezing when windows are occluded with FIFO/VSync enabled.

We need to get protocols into end-users hands quicker! The main reason many users are still using X11 is because of missing functionality that we can be shipping today, but is blocked for one reason or another.

Mesa MR to add support for the ‘frog-fifo-v1’ protocol :(https://github.com/misyltoad/frog-protocols)

  • merthyr1831@lemmy.ml
    link
    fedilink
    English
    arrow-up
    6
    ·
    4 days ago

    I like the approach here, but the requirements are a little vague and prone to bikeshedding. Stuff like “could this be used by multiple clients” might mean a protocol is held in limbo whilst it’s given extra scope for example.

    It’ll need some strong moderation which might rub people the wrong way, but if this keeps Wayland’s cutting edge moving whilst the official solutions are found, I’m all for it.

  • Gamma@programming.dev
    link
    fedilink
    English
    arrow-up
    3
    ·
    4 days ago

    Basically the Matrix Spec Change Proposal system, I like it. Opens the floor to more players, gives tool authors a list of protocols they could choose to build on, and hopefully compositors will choose to adopt or adapt one of these protocols before writing their own.