Michael added zero extra information on top of that.
The sad thing: I've been hearing/saying basically this for decades.
> The sad thing: I've been hearing/saying basically this for decades.
I don't think Linux distros will ever be popular compared to the commercial OSes, since for one thing to be popular nowadays you need to invest money in many things like branding and marketing so something is mainstream.
But looking in another way, in the past I would say that desktop Linux was dying, and nowadays it is more live than ever, so this is something.
Linux on the desktop is MUCH better now, it is improving but still no there yet. And I've been saying this very same phrase for decades now.
I don't care about a significant fraction of the desktop, but I'd love to enter a computer store and choose a hardware without severely limiting my choices.
After almost 13 years of development Wayland gains a (de-facto not even standardized) way to something as simple as taking screenshots / streaming. This is not "very good".
It was also never within the scope of Wayland to provide these kinds of APIs (previously when screen capture was available through the X11 interface, that was more of an accident than an intended feature, and it was an intentional design choice not to repeat this mistake in the design of Wayland).
Instead, compositors and applications (that use the Wayland protocol to communicate) were supposed to agree on a standard interface to do these kinds of things and then use that interface. And that's in fact what they did, by implementing the XDG desktop portal system (that's entirely separate from Wayland). I also see evidence of this interface existing as far back as 2016, although I didn't go digging for when it was initially invented.
Notice that this article doesn't say "is it now possible to screen capture when using Wayland", it only says that OBS Studio now uses this standard interface for screen capturing.
Of course, we have to consider that wayland is basically a re-thought for a substitute of a system that exists and evolves since early 80's... It is acceptable that it takes long. If such wait is needed to get something better than what we had and fix antique design limitations, I have no problem waiting for it.
Edit: EFF's recommendation for certbot, their ACME/LetsEncrypt client, is to use snap on a freaking server. Why?
I had lots of problems with snaps - slow loading times, mismatched styles, breaking with no decent error messages.
If you refer to the features described here, they might not be in any release yet and you might need to build from source.
Because I'd love a list of user handles of people who-- before this day-- have written variations of, "Wayland-based systems have been totally ready for use for years now." And maybe a browser extension that greys out comments from those handles.
Will there ever be a good way to run things like dmenu on Wayland? I'm still a novice, but will all X programs need to be converted?
No. Because Wayland is fundamentally different from X the following won't ever work:
* Window managers
* Programs that need to know their absolute window coordinates
* Windows that want to draw to the root window
* Programs that want to capture the screen via XGetImage()
> * Windows that want to draw to the root window
Gnome certainly won't support it, but in principle a compositor could expose that functionality.
> * Programs that want to capture the screen via XGetImage()
Yeah, doing anything via XAnything() only works on X. So you replace XAnything() by somethingElse().
I use the wofi which is the rofi replacement. Page 'i3 Migration Guide' [1] from the Sway wiki lists some dmenu replacements (bemenu, fuzzel, gmenu, wldash)
[1] https://github.com/debauchee/barrier/issues/109#issuecomment...
After almost 13 years of development the progress is rather embarrassing.
https://jonathanbossenger.com/obs-studio-linux-virtual-camer...
It doesn't seem to establish a connection properly with my Intel 8265 card out of the box though. I'll have to play around with it a bit more.
