honestly i kinda get their reasoning… it’s extra jank, extra complexity and a maintenance burden that shouldn’t be necessary if apps stopped dragging their feet about proper wayland support. niri instead focuses on the rest of the experience and honestly? they’re doing a pretty great job because it’s super fuckin comfy to use and customize, at least for me.

xwayland-satellite is the recommended way to run X11 apps, which are unfortunately still many, on niri. is that “setting my house on fire”? really confused here.

yeah really confused about that reply too. is using anything other than Gnome on Wayland “setting the house on fire”?

but i do have xwayland. please read my comment again.

mostly windows going blank or straight up refusing to show

issue closed != issue resolved though. it worked “a few” weeks ago for me too, and now it doesn’t. other people in fedi and one in that issue have the same problem, so it’s not like i’m alone with some weird setup here.

also i should note, although i did that in the linked issue, that other xwayland compositors do work. they’re just way more janky for running X11 apps seamlessly. so i’m not convinced the issue is elsewhere. i just didn’t press the issue out of respect for the maintainer and the only productive thing to do at this point would be to submit a patch if i am indeed right.

god i wish. half of my X11 apps don’t work, some that used to keep breaking out of nowhere.

Steam works through the XWayland compatibility layer

unless you use an environment that doesn’t support XWayland, like niri. xwayland-satellite used to be the easier route in that case but that seems to be broken now.

edit: wow i always thought people were being obtuse when complaining about “wAyLaNd sHiLLs” in their replies when criticizing Wayland. but now i’m not so sure.

None. Move your living room to the forest and never look back. Be free.

ragebait used to be believable 🚬

i liked their takes a lot, they didn’t hesitate to call out fossbro bullshit.

they need a break though. no way around it.

aughhhhhh here’s your upvote. git out.

see, i could maybe agree with this if it weren’t for the amazing work from R4L that already has been and continues to be done, despite subsystems maintainers putting their foot down and going “Not In My Back Yard, bucko!”. how many more maintainers does R4L have to lose before Linus realizes he might need to take a stance as a project lead?

ah, fair enough. i guess that’s kind of the thing with potential dogwhistles. if you know, you know.

i scrolled half a wiki page to link to… facts.

we don’t live in the 80s though. we live in contemporary times where things have different now meanings to what they did 40 years ago. meanings that might be influenced by recent happenings. hope that helps!

why they feel it’s Linus’ responsibility to make Rust happen in the kernel

who does? are you talking about marcan? because as far as i can see, what they’re asking for is for linus to make a stance and actually say whether R4L is a thing they want or not. because linus’ attitude so far has been “let’s wait and see” which hasn’t been all that helpful, as said in the blog post.

knowing where “thin blue line” comes from, you don’t see anything wrong with a maintainer randomly dropping it on the mailing list?

fuck gatekeepers. the linux kernel doesn’t deserve new, talented people bringing fresh, useful and modern approaches to the project; their time and effort is only wasted there. i know it’s not right, but part of me wishes linux rots and something better takes its place.

bitterness aside, i hope marcan gets the rest he needs. i wish him the best.

what would stop you from writing a quick proof of concept in each language to see how they feel?

i don’t think every developer hosts an actively transphobic discord full of dogpiling channers but i might be wrong on this one bestie