I used to run a multi-monitor desktop setup with Xorg, via the nVidia drivers. Two identical monitors, single framebuffer, no scaling, no tearing, single vsync.

One monitor, one framebuffer, an old use case that for some doesn't even exist now, inefficient and slow tearing prevention, laggy vsync.

That wasn't a multi-monitor desktop setup. That was a hacked together multi-display, single-screen setup.

Also why would you link an LD_PRELOAD attack? That's not Wayland-specific in any way. Any other protocol and library is vulnerable to that too. But let's point out one major issue with that: the LD_PRELOAD needs to be loaded in before the compositor in order to be relevant. With X, you can do that at runtime. Let's also read the README from the repository:

This program is in no way meant as criticism of the Wayland project. It simply demonstrates that creating a secure desktop requires more than just a few server-side restrictions.

Wayland isn't the only software we need for a secure desktop; it just handles making the display secure. For libraries and application sandboxing, you want Flatpak, and we're making progress on dynamic permissions there.

So? What's your point? Nothing here is a Wayland-specific argument. Your setup wasn't functional, it was fundamentally a hack, and one that not-NVIDIA/Intel/AMD hardware doesn't support. Your argument is falling flat on its face.

No.

Xorg doesn't support any of that. Multimonitor is nonexistent if you want to use it on a desktop, Xwayland still suffers from the lack of multimonitor (fractional+integer) scaling, and it tears horribly if you don't want to use inefficient and annoying vsync (Wayland's is fine).

Xorg is feature complete for its time; not for this time. The opposite goes for Wayland. Technically it's a "feature" that any application can keylog on Xorg, that doesn't mean that they should be free to do so without limit on Wayland too. If that means Wayland isn't feature complete and Xorg is, then so be it.

Yes, I am well aware of that. When someone refers to X, or Xorg, or X11, they're usually referring to bare metal X - you know, the insanely broken thing that people still want to use for some inane reason.

So what's your point? Why does this conversation continue to go on? It's clear that Xorg is unmaintained and will not be fixed, and Xwayland is the only thing that matters. Why argue it?

The ability to stop applications from keylogging you, secure and efficient screenshare, decent compositing, not to mention all of the cruft it's obtained over the years that stops it from obtaining all of these. And, as a whole, Xorg is completely incompatible with multi-monitor setups - no fractional scaling, and no multi-monitor scales, as well as refresh rates as you mentioned.

All we should be using nowadays at most is Xwayland. You only get a pass for bare X if:

1. You need accessibility tools that don't work on Wayland yet: https://github.com/flatpak/xdg-desktop-portal/issues/1046
2. You use some insanely old hardware that doesn't support the appropriate in-kernel and userspace APIs for Wayland to function.
3. You use NVIDIA, and can't feasibly use Nouveau.

Otherwise, get the fuck off of Xorg. The ecosystem has matured enough such that Wayland Just Works for basically everyone.

Possibly, but it sounds like a pain to work with, if I understand the technical details correctly.

The browser would need to be allowed to parse it, as they're the ones displaying the content; it would imply, however, that adblockers and other extensions would no longer be allowed.

you’re running a drm-compilant browser

They also don't want users to be able to use adblockers, that isn't all they're checking for. So this absolutely is the case. Their entire proposal is contradictory.

Nobody is actively working on it now; the same can't be said for Wayland. Recently, it even hit a development low of all time. The only ones working on it are the ones getting paid to work on it, and even then, only those familiar with the codebase. Looking at the history, the only major changes are for Xwayland, and aren't at all often.

If (almost) all of the developers have abandoned something in favor of a newer piece of software that does the job better, I think it's sufficient to say that it's deprecated and unmaintained.

No, I'm thinking of Xorg. The development on it has slowed to less than a crawl, and not because it's feature-complete. It's unmaintainable, and hell to manage for anyone that's not a senior Xorg developer.

The point of this is so that the user can't modify the site at all, despite what the proposal might say. Their goals and non-goals are contradictory.

Running this content in a container will not protect you. Just don't even try to adapt to it. Reject it completely.

Ironic how he chose an X in a strikingly similar style to the (old, unmaintained, and deprecated) Xorg. That was certainly a choice of all time.

That way should not be intrusive ads, and it shouldn't be tracking without user consent.

On their own, exposed to the user in an easily understandable way and easily customizable, they're not bad. They can even help; used right, you can get advertisements relevant to you and your interests, and developers can know what to improve on.

The problem is when this is abused to hell and back by companies that want to strip you of every penny they possibly can, without giving you the choice.

Note what I mentioned in the blog post: most will probably be fine with advertisements so long as they aren't annoying.

You don't get to act the victim when you actively hurt the UX by having avertisements that get all up in your face and want to eek out every single penny like we're slaves.

Non-obtrusive ads will always be the best :)

Or make them interesting if you want to be the focus. I can definitely say I've stayed and watched a few interesting advertisements.

I'd argue your viewpoint here is along the lines of opt-in telemetry - nice in theory, but not practical for the ones that need the information. And you can have respecting telemetry (as you can advertisements, just that nobody does so).

Coming from someone with an unstable source of income, and that can just barely get by: I'll take advertisements over a subscription/donation based model. Just don't flood your website with them. Or use shitty ad services. And don't make it an unusable experience cough britannica cough

Considering the amount of downtime I've seen with any somewhat large lemmy instance, I don't think that theory holds up

Doing everything explicitly can get to be annoying, especially when it comes to what you had to do before without Vulkan's VK_EXT_shader_object.

It's clear that some stuff should be implicit - most types in programming languages, for example; needing to specify a struct type and then the struct itself can be annoying - and other stuff explicit, like low level operations.

Returns are something that usually fall into that "implicit" category. Why should I do let a = function(); return a; when I can just do function()? It's shorter, simpler, and I don't waste keystrokes.

b

I hope NVK makes Nouveau a viable daily driver for NVIDIA users, they're already running games, and Zink is making large improvements.

Then we can finally get the hell off of Xorg and leave it almost entirely to Xwayland.

Don't forget being silly lil guys