Post AVda3aZdZqWZElQdsm by lanodan@queer.hacktivis.me
(DIR) More posts by lanodan@queer.hacktivis.me
(DIR) Post #AVdUGxZqlM2wcXWLiq by nergal@linuxrocks.online
2023-05-14T05:30:50Z
0 likes, 0 repeats
@marcan experienced #orbment by @cloudef and co quite early. (they also wrote #bemenu.) the experience was more impressive than when #aiglx first blessed xorg.
(DIR) Post #AVda3aZdZqWZElQdsm by lanodan@queer.hacktivis.me
2023-05-14T06:35:15.113705Z
2 likes, 1 repeats
@marcan Always makes me wonder a bit what would have happened instead if Wayland would have been named X12, forcing everyone to realize that the 11 in X11 was for the (major?) protocol version…
(DIR) Post #AVdhyajoL4lXvoJc9I by niclas@angrytoday.com
2023-05-14T08:04:23Z
0 likes, 0 repeats
@marcan Everywhere, it is the people least likely to do something that shouts the loudest.
(DIR) Post #AVdnTEzJkoIvDu0DVg by fristi@akkos.fritu.re
2023-05-14T09:05:57.192440Z
1 likes, 0 repeats
@marcan for shits and giggles, the xorg website should have a big warning on it's frontpage saying something in lines of "here be dragons from another age"I wonder though, why are some people so against wayland? Isn't wayland the ONE THING in the whole linux ecosystem that everyone's been waiting so long for?
(DIR) Post #AVeMUuZw6T6stpf9Dk by exa@mastodon.online
2023-05-14T07:31:04Z
0 likes, 0 repeats
@marcan half of the windowmanagers (esp. the nice unbloated ones, incl. xfce) still have no support... maybe it would be better to ask why is that
(DIR) Post #AVeMUvQkw5MRXeNKYC by untsuki@udongein.xyz
2023-05-14T15:38:21.220001Z
0 likes, 0 repeats
@exa @marcan Because WMs and DEs need to redo a lot of stuff to work with new protocol, probably. XFCE and a lot of other Desktop Enviroments devs are working on making that change, and new devs are making alternatives to minimalistic window managers they are used to
(DIR) Post #AVeXId30Ya0iY4bfEW by lanodan@queer.hacktivis.me
2023-05-14T17:39:00.939325Z
0 likes, 0 repeats
@jollyrogue @marcan How is Canonical relevant at all here?
(DIR) Post #AVed6R3hu7apcGVDRw by lanodan@queer.hacktivis.me
2023-05-14T18:44:01.702531Z
0 likes, 0 repeats
@jollyrogue @marcan Ah yeah right, forgot Mir wasn't wayland…
(DIR) Post #AVehO0eBEyz0jNCKiO by smonff@plush.city
2023-05-14T19:31:39Z
0 likes, 0 repeats
@lanodan oh, do you remember Perl 6?
(DIR) Post #AVehO2ApZ4h7SvTvFI by lanodan@queer.hacktivis.me
2023-05-14T19:32:02.488479Z
0 likes, 0 repeats
@smonff Very different story that one.
(DIR) Post #AVfuCQiDzwPUeqrHPM by whiteline@shitposter.club
2023-05-15T09:30:47.490941Z
0 likes, 0 repeats
@marcan @burlveneer the versions packaged by e.g. debian stable are what's relevant for discussion and you know it
(DIR) Post #AVhIaCsnevvEm5dS64 by lanodan@queer.hacktivis.me
2023-05-16T01:38:13.980696Z
0 likes, 0 repeats
@marcan @elilla @lunabee In fact it is supported in sway: https://github.com/swaywm/sway/wiki#load-custom-xkb-keymap-file-since-3999
(DIR) Post #AVhIee7AM1oWOHTJAW by nroach44@mastodon.social
2023-05-14T04:19:44Z
1 likes, 0 repeats
@marcan the only issue I've had is that Xwayland doesn't do X over TCP, so my 30 year old logic analyser doesn't work, but I'm not about to make that someone else's problem.It really bugs me when people decide to stick to an old thing and then decide it's society's fault for moving away from it
(DIR) Post #AVhInoheM8UdpuuStU by ids1024@fosstodon.org
2023-05-14T05:41:13Z
0 likes, 0 repeats
@nroach44 Clearly not an appropriate logo such a repository. It should instead be the XOrg logo but with a blue X encircled with a pink-white gradient. That would communicate "xtrans" more effectively.
(DIR) Post #AVhInpH6EKqjbrUm9I by sima@chaos.social
2023-05-14T08:27:15Z
1 likes, 0 repeats
@ids1024 @nroach44 you mean like this
(DIR) Post #AVhInqwG2nMmlnl9wO by sima@chaos.social
2023-05-14T09:15:30Z
1 likes, 0 repeats
@ids1024 @nroach44 oh I actually attached the wrong one, you wanted the other one I think
(DIR) Post #AVhIvLb4SJiJskQIyW by alanc@fosstodon.org
2023-05-15T05:43:33Z
1 likes, 0 repeats
@sima @ids1024 @nroach44 but the current one doubles as an architectural diagram - the blue layers are the client & server program code, the pink layers are the client & server sides of libxtrans, and the white layer is the OS socket interfaces.