3 ms·
If I were PM for a consumer-facing product, number 2 would be a blocker for me and a critical issue. It's such a basic, common, everyday use case that it's mind
by Sakos 4y ago
If I were PM for a consumer-facing product, number 2 would be a blocker for me and a critical issue. It's such a basic, common, everyday use case that it's mind-boggling to me that they're dropping the ball on it.
- orwin 4y agoAt my previous job, we actually recorded screens of users (and kept activity records ~3months). We couldn't serve them wayland, but X11 was enough (it was mostly datascience) (And by the way, it was only in one of our offer, the most expensive one, and sold as a feature, it was not some shady stuff)
- berkut 4y agoEspecially in the era of working from home now: I regularly need to share my screen to demo stuff, or record screen recordings of WIP prototypes... Even for code reviews sometimes it's easier to do it via screensharing with a full IDE for jumping around the code...
- nhumrich 4y agoYes, I was using Wayland fairly comfortably but am now using x again thanks to screen sharing and all the different conference tools everyone uses.
- dralley 4y ago#2 is a solved problem. I use Wayland and screen sharing works fine for every app I use (browser-based video chat, OBS). The problem is adoption of the new APIs, not the lack of a solution.
- vetinari 4y agoFor 2, APIs exist. It is up to the apps to use them. So if you were PM, the ball would be on your side.