261–270 of 714 posts
Earlier quoted context omitted.
I get your point. But until those benchmarks at least correlate with behavior users see, they are not worth much.
I don't know what you're trying to say, outside of some vauge attempt to avoid admitting a mistake.
Nobody cares about benchmarks that a) don't exist or b) are not indicative of what folks will experience.
Better to say both X11, and Wayland are now two pieces of abandonware.
I really hate to say it, but Canonical was and still is correct with starting Mir.
People who were in the fence about supporting Wayland were now even more convinced they should ignore it. That's one of the reasons a decade later you still have this much FUD.
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 turned off selinux temporarily and activated the connection successfully, and determined that it was indeed SELinux that was preventing NetworkManager from doing its job.
then i re-enabled SELinux went to look at /var/log/audit/audit.log to see what it had to complain about and indeed some files created by NetworkManager in /root/.cert had bad contexts.
I set the proper contexts (semanage fcontext -a -t ), applied them (restorecon -Rv /root) and all was well.
SELinux was initially scary but:
- The "SELinux for mere mortals" talks are very informative introductory video (https://www.youtube.com/watch?v=_WOKRaM-HI4)
- The SELinux User's and Administrator's Guide from Red Hat was a deeper explaination (https://access.redhat.com/documentation/en-us/red_hat_enterp... -- linking to rhel 7 because that's what i read at the time)
I had to study this stuff in order to get Red Hat certified (RHCSA, passed with 300/300).
Getting certified is absolutely worth it. Getting certified is the difference between "10-15 minutes to get a diagnosis" and "I gave up on SELinux about 20 years ago".
Earlier quoted context omitted.
I really hate to say it, but Canonical was and still is correct with starting Mir.
Canonical announced Mir out of nowhere in an attempt to gain control just like they are trying now with Snap. After the announcement of Mir their developers went to IRC and made abundantly clear they had no idea how Wayland works and that Mir was useless. Where is Mir now? Using Wayland. People who were in the fence about supporting Wayland were now even more convinced they should ignore it. That's one of the reasons…
It could have not gone that way. Now we've got two equally bad alternatives out there.
> That's one of the reasons a decade later you still have this much FUD.
I don't think you know what FUD means.
Earlier quoted context omitted.
> No, there are protocols to negotiate whether an app has server side decoration or not and the compositor has the last say. The compositor can implement that protocol and just respond with "this compositor doesn't support SSDs". GNOME does this, so all toolkits must use CSDs if they wanna work on the most popular Wayland compositor. Incidentally, that's hell for all the simple libraries out there which just exist to…
GLFW and SDL are looking at using libdecoration to draw CSDs. Yes it's an additional dependency but most applications won't need to worry about it unless they need it. The way GNOME is built it's not really possible architecturally for them to support SSDs in Wayland. Maybe that will change if they ever get around to redesigning mutter and gnome-shell, but I wouldn't wait for it.
Earlier quoted context omitted.
I love how people say that an unified method of taking screenshots, screen streaming, screen recording and performance in general is legacy baggage.
Those standards need to exist, but those standards do not need to exist as part of the display protocol. People make this mistake over and over and over. Nothing prevents the compositor writers from deciding on a common API for screenshots and similar things (and there has been movement in this direction)
They do. It's pointless fragmentation otherwise.
Earlier quoted context omitted.
It's not a particularly arduous "adventure". We maintain a list[0] of programs which use these protocols. And wlroots != tiling window manager: there are multiple wlroots-based compositors which do not use the tiling paradigm, the most developed of which is probably Wayfire[1]. [0]: https://github.com/swaywm/wlr-protocols/wiki [1]: https://github.com/WayfireWM/wayfire
Apologies; I misunderstood one of your links and thought sway had been renamed to wlroots. To be clear the "adventure" I'm talking about is for replacing desktop environment niceties like the ones provided by gsettingsd and the tight integration provided between devices and the system management tools offered in full desktop blown environments like Gnome and KDE. I used i3 for six or seven years and it was never as n…
Gnome will catch up some day.
This desperate push by Wayland people is putting me off of Wayland. You can't FUD a software into being dropped in favor of yours.
Earlier quoted context omitted.
OS: OpenBSD Phone: Nokia8110 Watch: Vostok or Raketa
I was just thinking that, if X.org truly were abandonware (I have no basis to accept or reject the opinion reported in this article), OpenBSD becomes a bit of a haven. My understanding is that Wayland does address some security issues in X11, but that Xenocara (OpenBSD’s branch of Xorg) also attempts to address the security of X11 in a way that integrates with the rest of OpenBSD’s security mitigations. OpenBSD is a…
Exactly! And Xenocara. And Upgrades are painless.
Earlier quoted context omitted.
We do need some form of signal that indicates a project has a maintainer though. It doesn’t matter that he has been inactive for 4 years (on that project), but if I submit a PR, it’s nice if there’s someone at the end of the line.
Repos could really have exactly that. A dead man's switch that asks you every, I don't know, three.to six months - via email even - "you good for this repo still?". You answer with a click "yup" and that's it - a signal on a repo on github or whatever that says "still alive". Otherwise "uh oh - we need help" and then a mechanism there to immediately offer alternative forks with a good enough signal "strength". It's l…