Conversation

Okay so the hilarious thing is, one year ago I wanted to use Linux as a desktop operating system, so I was really angry Wayland was not designed to enable writing GUI applications for Linux. Wayland seems to have been designed as a kind of super-EGL, a surface negotiation protocol for embedded touchscreen devices. Now one year later I want to get Linux off my computer at any cost and I'm going hmmm so you're saying your surface negotiation protocol has NO Linux baggage…?

https://app.wafrn.net/fediverse/post/01a17ad8-0a53-72af-91bd-6b91e7c25b7a

3
0
0

This was what I thought for about 15 seconds and then it was explained to me that while Wayland treats the Linux *desktop environment ecosystem* like a total stranger, it apparently freely takes dependencies on a wide variety of very specific Linux kernel quirks and

(EDIT: I think some linux desktop specific freedesktop/XDG daemon that was mentioned the last time I asked about this on here, but that's being questioned so now I'm not sure?)

4
0
0
@mcc it definitely does not require systemd (and in fact has nothing to do with systemd at all)
0
0
1

@mcc me: please give me a pointer to a framebuffer with the pixels in the order they will appear on the screen

Wayland: that’s to hard. here are some extension protocols I think you’ll like. do you like this

1
0
0

@joe @mcc compositor: isn't there somebody you forgot to ask?

1
0
0

@joe @mcc people misunderstand wayland to be a sort of replacement for x11 and glx. this could not be further from truth. wayland is a replacement for corba that happens to implement a replacement for icccm as a bonus

1
1
0

@mcc "it's inaccurate enough that i would only say that as a joke, but it's not so inaccurate that it becomes misinformation" is what i'd say

1
1
0

@mcc one of the really really nice things about wayland is that it doesn't couple the window server and the GPU, meaning you can render any window on any GPU and graphics stack, or even in software. furthermore the GPUs can be hotplugged and hot-unplugged

this was de-facto unsolvable on Xorg and this problem alone is enough to leave it in the past

2
0
0

@whitequark @joe @mcc didn’t Berlin use CORBA? or am I misremembering? the thing that was Wayland before Wayland.

1
0
0

@arjache @joe @mcc i'm not actually familiar with the predecessor, i concluded that CORBA was involved in some capacity at some point entirely on vibes. if i'm actually correct about that this makes my post like 10x funnier

1
0
0

@mcc@mastodon.social @whitequark@social.treehouse.systems

As the person who made the post that mcc is quoting I am just going to declare it true purely because I think it's funny. /j

1
0
0

@daemonspudguy @mcc after being informed that wayland's predecessor, belin, literally used CORBA i will upgrade my statement to "yeah it's basically true"

0
0
0

@mcc why can't I have surfaceflinger but without depending on bionic libc

1
0
0

@bob I'd guess because anyone who has the power to make that possible is professionally required to stay committed to Android lock-in?

1
0
0

@whitequark @mcc I am glad that this is working for you and I agree that Xorg (not X11! wayland speaks X11 and could have just been an X11 server initially) had several serious technical limitations that did need to be addressed, and even some of the “security” stuff is kind of real (even if botched)

but, as a developer, I need to know or change the absolute coordinates of a window far more frequently than I need to hotplug a GPU

2
0
0

@glyph @mcc yeah you're right, i edited the post

re: absolute coordinates: more or less yeah. i think "other-window-relative coordinates" (a proposal that i think is currently still WIP?) are what most applications with complex toolbar, etc needs want (this is how it's often expressed internally), and actually absolute coordinates are needed mostly by one thing, wine

but i also consider wine an absolute requirement for a platform to be usable to me

2
0
0

@mcc didn't google just fire a bunch of people

1
0
0

@bob then possibly you can't have it because nobody knows how to make changes to surfaceflinger

0
0
0

@mcc@mastodon.social @whitequark@social.treehouse.systems @glyph@mastodon.social

It drives me fucking insane whenever people conflate "X11" with "Xorg." Especially when Xorg wasn't even the first X11 server implementation nor is it the only living one. And no I'm not talking about the fascist idiots behind Xlibre either. There have been multiple implementations of the X11 standard, several of which are actually better than Xorg ever was. Granted others were XFree86, which sabotaged itself in spectacular fashion by adopting the obnoxious advertising clause. Xdec, Xsun, AIX X11, the X server on Apple's A/UX, and XQuartz were all different implementations on various Unices of the time. Xming still exists on Windows.

2
0
0

@daemonspudguy @whitequark @glyph Hi, moderate-to-heavy Solaris user here, ex-Sun employee. I have used many X implementations and never been specifically happy with a single one of them

0
0
0

@daemonspudguy @mcc @glyph i have no excuse for this besides "it's like 2am here and i'm tired"

2
0
0

@whitequark @mcc my biggest criticism of wayland has nothing to do with any particular technical choice about how things got implemented, it’s how they were documented and, crucially, how they were *rolled out*. the experience of figuring out the recommended migration path for anything feels like looking for secrets in a Wolfenstein level. I just run around bashing into everything at random in the hopes that I will find a hint that leads me to a treasure. also, nazis all over the place

3
0
0

@glyph @mcc yes many of these decisions were and still are horrendous

0
0
0

@daemonspudguy @mcc @glyph a little bit but i'm not upset about it or anything. perhaps at myself, because i should actually know better

0
0
0

@whitequark @daemonspudguy @mcc fwiw I think the distinction is important but at this point for me it’s one of those errors like saying “can I” instead of “may I” when asking for permission. like yeah there’s a difference and sometimes it’s important but everyone constantly conflates them, it’s no big deal as long as you can clarify when necessary

1
0
0

@glyph @daemonspudguy @mcc it's more upsetting because like, i tried to patch nvidia's hot-unplug support into xorg. it's not a theoretical!

2
0
0

@glyph @daemonspudguy @mcc i do not recommend doing that by the way, it's a horrifying rabbit hole full of reverse-engineering nvidia.ko (ok i guess they open sourced those bits now)

0
0
0

@glyph @whitequark maybe they'll write useful documentation if we tell them our AI code assistants need them

1
0
0

@mcc @glyph fwiw i think i understand enough about wayland to be able to assist in deciphering wtf it's doing

1
0
0

@whitequark @glyph let me get back to you about this in approximately 23 months

0
0
0

@mcc@mastodon.social @whitequark@social.treehouse.systems @glyph@mastodon.social

There are at least two endings I can perceive for such a goal: giving up because Nvidia can't make comprehensible code to save their lives or being rejected with the only justification being "X is dead, kid."

1
0
0

@daemonspudguy @mcc @glyph when i talked about this on i was literally told that (paraphrased) we all moved to wayland, nobody cares about xorg except as xwayland

i tried to do it anyway and ended up hitting an annoying segfault in NVRM that i needed a lot more context to fix. so i gave up

2
0
0

@whitequark @mcc seems to have the opposite effect on the compositor end, though, since every smaller-scale wlroots compositor I’ve seen seems to need a whole wiki page dedicated to Nvidia users

but maybe now that cow is a thing, there’s less need for every would-be window manager to reinvent the graphics HAL

1
0
0

@joe @mcc the nvidia situation was a fiasco

1
0
0

@joe @mcc it sucks particularly because i think nvidia had a good point with eglstreams, and it had a good point with their x11 stack. it wasn't just being fickle for the sake of it, as people portray it sometimes. but it still created very real pain to end users

0
0
0

@mcc@mastodon.social @whitequark@social.treehouse.systems @glyph@mastodon.social

Ah so the secret third option: both simultaneously.
I love computer.

1
0
0

@daemonspudguy @mcc @glyph i actually got as far as "if you hot-unplug the prime render offload nvidia gpu from the thunderbolt port, and you aren't currently rendering graphics, xorg doesn't immediately crash"

1
0
0

@daemonspudguy @mcc @glyph and i patched enough of the kernel driver that you could unload and reload it without effectively deadlocking the kernel

1
0
0

@daemonspudguy @mcc @glyph in the end i solved the overarching problem by buying a steam deck

0
0
0

@whitequark
As an end-user I don't want apps to have access to absolute positioning given how much I've seen things break with those once you have a non-standard screen layout.

The "zones protocol" (which I believe is merged now) should provide the best of both world imo. Allowing apps freedom of positioning, but only within an area controlled by the composutor/user.

This being years late is a real problem ofc.

(I would link the design documentation for the protocol but attempting to seatch for it on my phone is making my phone oom)
@glyph @mcc

1
0
0

@robin @glyph @mcc oh it's finally merged, thank fuck https://wayland.app/protocols/xx-zones-v1

i still think absolute positioning needs to exist for wine (because things break otherwise), but i won't cry if nobody else has it

0
0
0

@mcc this is a really interesting thread, thanks

also the corba stuff is making me catatonic

1
0
0

@autumnwinds corba was a good idea i'm just not sure it was… you know… good

0
0
0