FOSS purists are too busy malding over systemd, and Steam being proprietary DRM, and games being closed-source.

Me. I lied, it’s totally real.

It’s a doctored screenshot, it’s not real.

My setup is two screens side by side and one above. KDE Plasma 6.1 can handle it without issues, and you can make panels on any screen.

One of the most significant drawbacks of Wayland is feature fragmentation between compositors. Unlike the X11 stack of X.Org server + window manager + compositor, Wayland compositors have to implement all of Wayland in themselves. They have to serve as the display servers, plus manage window positioning, plus render the clients, and all of that within the confines of Wayland-protocols. Building a compositor is a massive task, which is why middleware like wlroots is such a big deal. It also means that WM-agnostic tools like xrandr and xdotool are more difficult, sometimes impossible to implement.

Consider that Wayland is still heavily under development, and that new protocols have to be implemented by every compositor separately, and that the development of wayland-protocols is an ongoing fucking trainwreck – fragmentation is inevitable, and some compositors will not have the same functionality as others (GNOME being a particularly nasty sandbag). Similarly, things that don’t work as expected in one compositor might work perfectly fine in another.

Right now I would consider KDE Plasma to be the most feature-complete compositor that is also beginner-friendly.

Meanwhile you get the one thing X has: It works.

You mean I’ve been doing everything, from work through CGI to gaming (with 120 FPS mind you) on a display that doesn’t work?

Wayland has many issues, sure, but it’s not even close to the point where “it works” can be used to distinguish it from other display protocols. We (and by we I mean anyone willing to dedicate their life to it) could do a lot to bring X11 up to modern expectations, but it’s just not worth the effort. X11 will outlive the cockroaches, but claiming that Wayland is not a functional display protocol is incorrect and uninformed.

X has been around forever, it sucks

That right there. X11 was released in the mid-80s and has become an unmaintainable patchwork of additions. Nobody wants to develop or maintain the code because changing one thing breaks five others.

Wayland also takes advantage of 3D acceleration, since each window is a plane rendered in 3D space. There’s no longer a choice between massive input lag with a compositor and massive screen tearing without.

Worked wonders for the Yuzu developers.

No idea, I never used it. The day I got that phone, I disabled/uninstalled all Smasnug and most Google apps.

You could try getting the APKs from APKMirror and installing them from a file manager.

They could be, easily. Sony wouldn’t likely win, but all they really need to do is bury the operators in legal fees and subpoenas.

Settings, Apps, Galaxy Store, Disable. It should revert it to the stock version and disable it. Unless your phone has some additional restrictions that prevents disabling it.

What do you suppose they should do instead? Get sued out of existence?

I’m sorry, the fucking wha– oh right, the first app that I disabled and hid on my last Smasnug.

Important addition: don’t just shut the fuck up.

First, in some jurisdictions, failure to identify is an arrestable offense. Full name, date of birth, relevant cards/papers.

Second, if you need to reach for something, say something so they don’t think you’re about to pull a weapon on them. Officer safety is always a concern in the land of handing out guns like candy.

Third, explicitly state that you are exercising your fifth amendment rights. Otherwise you might run into an “I want a lawyer, dawg” situation.

Free speech has to be absolute

Movements such as (removed irrelevant part) shouldn’t be supported

Make up your mind, my dude.

Reading further into his… thoughts… I think he’s far beyond what I would consider “unhinged”, and considering his 14th point, probably in possession of hard drives that authorities might want to investigate.

I also discovered that there was a Slovak MEP by the same name who was really passionate about chicken legs.

Gay the pray away and save a christian!

It’s okay, disability discount is available for everyone with a peg leg, eyepatch, or hook hand.

My full-time job literally involves dealing with systemd’s crap. There is a raspberry pi that controls all of our signage. Every time it is powered on, systemd gets stuck because it’s trying to mount two separate partitions to the same mount point, whereupon I have to take a keyboard and a ladder, climb up the ceiling, plug in the keyboard, and press Enter to get it to boot. I’ve tried fixing it, but all I did was break it more.

I’ll preface this by saying that I’m a Wayland user (Hyprland, then KDE Plasma, and I’ll be giving Cosmic a fair shot), and don’t see myself returning to X and having to choose between massive screen tearing and massive input lag.

Wayland is missing many features that are required for some people or some applications. There’s no way for a multi-window application to tell the compositor where to place the windows, for example to have one window snap to and follow the other. Color profiles were implemented very recently. Wayland’s isolation of applications, while a significant improvement to security, has made remote input software and xdotool-like programs highly dependent on third-party interoperability solutions (specifically dbus and XDG Desktop Portal). The same isolation broke most accessibility tools like screen readers. Dockable windows, like the toolbars in QT Creator or QOwnNotes, are often difficult or impossible to dock back into the main window.

Because Wayland compositors have to implement all protocols (as opposed to deferring to the X.Org server; which is why wlroots is such a big deal) or rely on XDG Desktop Portal (which has never worked right for me), feature parity between compositors is never guaranteed, and especially problematic with GNOME dragging its heels.

Wayland is nowhere near feature parity with X11 today, and that is a legitimate prohibitive issue for many people. Wayland will never reach total feature parity with X11 in some areas, and that will always be prohibitive for some people.

But the worst (in my opinion) is the development process of the Wayland protocols. The proposal discussion threads read like the best and/or worst sitcom you’ve ever seen. It took them several months of back-and-forth just short of ad hominem attacks to decide how a window should set its icon. Several months for a pissing WINDOW ICON!

[     *] (3 of 3) A stop job is running for User Manager for UID 1000... (1m12s / 3m)

TMI had zero fatalities, minimal release of radiation, and no measurable effect on health. Residents of the area were exposed to less radiation from the accident than the yearly background dose.

Some layers of safety failed, but the rest did their job. That’s why we call it an accident and not a disaster. The plant continued to operate for decades with no issues. The only reason it’s so prevalent in the public consciousness is because of faulty reporting and irresponsible, ignorant people (like you) parroting the first thing they hear from sensationalist media.