Post ASAkcXmHaq8Goud0Sm by xerz@fedi.xerz.one
(DIR) More posts by xerz@fedi.xerz.one
(DIR) Post #ASAkcWVEKktirjdsFE by xerz@fedi.xerz.one
2023-01-30T15:08:55.365557Z
0 likes, 0 repeats
HOLY SHIT THAT’S SAVAGE AS HELL https://www.youtube.com/watch?v=RIctzAQOe44
(DIR) Post #ASAkcX9duVDwt4Y9Ee by xerz@fedi.xerz.one
2023-01-30T15:09:47.136743Z
0 likes, 0 repeats
This was in 2013, the poor guy didn’t see what was coming :blobcatderpy: (also comes to show how people used to associate their perspectives on software design with their political ideologies… not sure that one has changed much)
(DIR) Post #ASAkcXmHaq8Goud0Sm by xerz@fedi.xerz.one
2023-01-30T15:10:58.290166Z
0 likes, 0 repeats
(BTW: that’s an AV1 video. If you can’t watch it, make sure you’re on the latest version of your OS and open the link to watch on my instance)
(DIR) Post #ASAkuBspjbPM826gYi by xerz@fedi.xerz.one
2023-01-30T15:13:54.594451Z
0 likes, 0 repeats
(…I can’t believe I made the video heavier and more confusing by leaving, like, one extra frame of the camera view moving, oops)
(DIR) Post #ASAl6loBzX9r1VvzcG by xerz@fedi.xerz.one
2023-01-30T15:16:25.579190Z
0 likes, 0 repeats
(…it’s 1KB in difference, eh)
(DIR) Post #ASAuAiuDcotIlZiGeW by vertigo@hackers.town
2023-01-30T16:54:49Z
0 likes, 0 repeats
@xerz I'm not sure I understand what came between 2013 and 2023, other than the inability to run tools like OBS Studio because of Wayland's default approach to handling desktop security. I'd imagine once that was satisfactorily resolved, Wayland uptake would start to pick up, yes?
(DIR) Post #ASAuAjWrJ9nchPn7se by xerz@fedi.xerz.one
2023-01-30T16:57:35.535080Z
0 likes, 0 repeats
@vertigo What’s bad about the approach? OBS Studio has been working for like 2 or 3 years by now, all you need to do is click on a menu just like either of these (it’s called a “portal”) and it’s remembered for future sessions
(DIR) Post #ASAuG3wSqAMTSOJEbg by xerz@fedi.xerz.one
2023-01-30T16:58:37.645546Z
0 likes, 0 repeats
@vertigo (also, you can setup portals that basically disregard the most basic of security concepts and just pass any petition created… but that would be insecure indeed)
(DIR) Post #ASAv0sOTat5PFdjaAS by vertigo@hackers.town
2023-01-30T17:01:26Z
0 likes, 0 repeats
@xerz Well, that just reinforces my question, then, doesn't it? I'm clearly not up on outstanding Wayland issues, and clearly the OBS issue has been resolved.But, once upon a time, with Wayland, you only had access to the bitmap data for your windows only, with no provision to gain access to the screen or to the content of other windows. So, you couldn't share screens. Good to know that has been resolved now.However, your post implied that other issues remain unresolved, and I'm not aware of what those issues are (other than, maybe, simple inertia).
(DIR) Post #ASAv0sp402Lya6Aobo by patrick@georgi.family
2023-01-30T17:05:06.706617Z
0 likes, 0 repeats
@vertigo @xerz inertia, but also random issues like seamless interaction with old x11 apps, accessibility, internationalization (e.g. pinyin input), input devices beyond basic keyboard and mouse, ...All that stuff that was worked into xorg for the last 25 years and now had to be rediscovered one by one.Every time somebody runs in some issue (no matter how minor) that resets the clock for large distros to switch over. It's only recently that some decided to go all.
(DIR) Post #ASAv0tHQIb2S03RSoS by xerz@fedi.xerz.one
2023-01-30T17:07:23.290420Z
0 likes, 0 repeats
@patrick @vertigo Doesn’t seem like IMEs are an issue at all, I have used Anthy and Mozc through Ibus just fine on GNOME. Input devices are perfectly fine as well, at least in regards to drawing tablets and multitouch displays.Overall, I’m not sure what’s missing these days compared to X, other than maybe accessibility features like screen reading (which I’m not properly educated on) ‒ and I didn’t mean to imply there were big issues. Sure there’s work pending, but these days we’re talking about HDR or polishing fractional scale, or how implementations like KWin’s are squishing bugs to this day. That’s pretty much it.
(DIR) Post #ASAvL6cgOrYTAq1dPU by xerz@fedi.xerz.one
2023-01-30T17:10:55.873547Z
0 likes, 0 repeats
@patrick @vertigo (it’s worth noting: Wayland is, unlike X, just a protocol on its own, without a reference implementation everyone uses. Inertia issues were worsened, indeed, by the fact everyone had to implement stuff on their own. But that doesn’t seem to have come as a surprise to Wayland authors, and it’s about time.)
(DIR) Post #ASAvTQZg6XkXMwaWMi by vertigo@hackers.town
2023-01-30T17:11:22Z
1 likes, 0 repeats
@xerz @patrick That sounds like good news overall to me. I'm all for simplifying the display stack if at all possible.Maybe one day, I'll gain the courage to explore/experiment with Wayland compositors.
(DIR) Post #ASAwF7fbh4UQdd6Vdo by xerz@fedi.xerz.one
2023-01-30T17:21:08.750853Z
0 likes, 0 repeats
@vertigo @patrick If you’re curious and it helps: you can usually open a nested compositor (Wayland inside X) if you’re bored enough, it’s almost like a VM :blobcatsip:GNOME: dbus-run-session gnome-shell --wayland --nestedKDE: dbus-run-session startplasma-waylandwlroots-based (Sway, Wayfire, etc): just run as usual (I think)