201–210 of 714 posts
Earlier quoted context omitted.
When a window bar needs a gradient, you are starting to stress the graphics engine... And that is just a simple bitmap (or not)...
http://xopendisplay.hilltopia.ca/2009/Jul/Xlib-tutorial-part...
Oh, look, more non-experts spreading misinformation about Wayland on HN. Must be Sunday. https://drewdevault.com/2019/02/10/Wayland-misconceptions-de...
Is there a summary somewhere of what's wrong with x.org/x11? I haven't been keeping up.
If Wayland is the future, the future is grim. People often complain that Wayland is taking a long time to catch up to X11, but that actually stems from a deeper issue: Wayland has a horrible design, for an X11 replacement, a design that leads to massive fragmentation issues across the graphical part of the Linux ecosystem. Implementing a Wayland compositor requires much more effort than implementing an X11 window man…
> Wayland is also, with its forced composition, hostile to interactive applications requiring low latency, e.g. video games. https://www.gamingonlinux.com/articles/gnomes-mutter-gets-fu...
Does Wayland support this?
Sure X.org is abandonware but there are serious problems Wayland still hasn't solved that X has. 1) Wayland is really slow. I don't know if it's the compositing or what but it's unusable on lighter hardware that X ran fine on. 2) Widget toolkits handling window decoration is awful. Before the large number of toolkits just meant some controls were a little different but now basic behavior changes based on how programm…
The X11 protocol is the surface you need to maintain but swapping the internals should be do-able. Maybe we should have some call to action or reverse-auction or something. I'd love to support a viable path forward (I feel this effort would be a bit like neovim).
Personally I think it could start as a Xephyr or Xnest type project (to allow you to run rootless X) and then extend it with a from-scratch protocol that slowly replaces X (starting with support for simple but useful applications and going from there).
But clearly I only barely know what I'm talking about. Probably the reason things are the way they are is because of how the whole OpenGL / Vulcan etc. thing is not resolved, so any potential replacement has no foundation to build on (but this is something I don't know anything about).
Earlier quoted context omitted.
Most of X.Org is horrible and the entire system is unmaintainable. It is hard to even get maintenance releases for it released, as the article alludes to. Development hasn't stalled because people think X is good. Development has stalled because the fundamental design is so misaligned from the modern graphics stack that improvements are not worth attempting.
The thing is, X.Org server is not X11 the protocol. X11 could be easily implemented on new driver framework supporting new graphic stack. Instead we got a piece of sh*t that is fitting for a custom embedded device or some closed environment, but not an X11 replacement.
Earlier quoted context omitted.
just yesterday i set up a vpn client very easily by running nmcli connection import type openvpn file myconfig.vpn the only issue that i had was SELinux doing its job, and was quickly fixed. Even easier than with the usual gui tools.
How did you find SELinux was doing its job and how long did it take? I gave up on SELinux about 20 years ago when it was a source of endless frustration, or was that 15?
I agree working with selinux is a bit of a PITA but if you learn sealert, ausearch, and/or audit2allow it can severely reduce the pain and allow you to keep selinux enabled. I really like this page personally: https://wiki.centos.org/HowTos/SELinux
Wayland's poor screen sharing support in these days of WFH is a big issue.
I try to steer everyone toward Google Meet if possible, and unfortunately for the others, I have a decent amount of sway :-D
Earlier quoted context omitted.
> screenshots don't work – they do. I use them all the time. they don't work on wayland, they work on specific compositors that implement an extension.
Are there even any Wayland compositors in actual use that don't support that extension?