under the definition of bike shedding in the Encyclopedia you'll find wayland the prime example. been waiting years on one pr for them to decide on the word "may" vs "will"
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
It drives me crazy. Just release it 18+months ago and iterate with versions, at least your users will have the feature in their hands.
[This comment has been deleted by an automated system]
It is kind of shooting at the ambulance, zoom needs to also adapt to the new API. The alternative is a completely non functional Wayland for videoconferencing for years... Unusable stable is not better than unstable usable IMHO at least you have a shot at fixing it for the second option.
decide on the word "may" vs "will"
I assume they went with way land as a compromise.
I hope this can mean I can use my android tablet as a 3rd screen with vnc with usable lag and frame rate
Pipewire works well enough for sharing screen even though it isn't well supported by shit software like Slack. Would this replace it?
No, most likely Pipewire would be used to implement the protocol for various compositors.
Think of the protocols as high-level descriptions of interfaces (or designs) that specify what needs to be implemented to support a particular feature (in this case capturing images of a "screen"). Looking at this one, it describes a ext_image_capture_source_v1
object that has various methods such as create_source
and destroy
. Different compositors could then implement or support this interface with whatever technology they wish (most will rely on Pipewire).
This is already the case with the existing screensharing protocol. For instance wlroots uses pipewire buffers in xdg-desktop-portal-wlr.
So... does THIS mean that this doesn't support explicit sync, right as explicit sync is about to be stable and supported in the NVIDIA 560/565 drivers? As far as I know there are currently other ways to do screen capture outside of this protocol on Wayland so its not like there are no interim solutions, why release this when it is essentially still incomplete?