Ok, but what’s the situation in this one?

Bat?man

Ootl, What’s this?

What disconnecting problem?

My system should be fully updated, I will try an Xbox 360 cabled controller

That’s a flattering thought, but I think that kind of improvement is a pipedream.

The os shenanigans might be the reason tho

You are correct, it also lacks a decorative groove that the “one” one has near the top.

I think the “series” d-pad is the best modern d-pad, especially since Nintendo forgot how to make them just before releasing the Wii u. I’d say on par with classic Nintendo d-pads, maybe a bit less comfortable for platformers though.

On the other hand, the 360 d-pad is the worst most horrible piece of crap ever devised.

I am seeing higher latency even plugged via cable though, even if less so

No, kde on amd

yeah, but the point of a platform are the applications it supports, you don’t want to be The King of Nothing. If even after buying into wayland, applications still work bad on gnome because they expect to get support for X, than gnome needs X or to give a better option (better for the applications, not just according to themselves).

PING. Commenting just for the notification. I edited to respond to the other points but in the meantime you had already answered.

The point 2.1 “less to implement in the compositor” doesn’t apply, because for xwayland go work (which is intended to stay around for the foreseeable future) mutter still needs to implement SSD, it’s only skipping on implementing the Wayland SSD protocols.

Points 1 and 2.2 are not strong points. “We do <thing > because we always did before <thing 2>” is not a good point. For example, after all, we always used X10 before Wayland, and we always did implicit sync before last year. And compositor shouldn’t limit programming styles, they should support as many things as possible, and let the application decide their programming design. Plus, most modern applications on windows and macos embed a copy of chrome to display a single offline Web page, but I don’t see you suggesting we replace compositors with browsers.

Point 2.3 is also weak because most of the things a compositor does are already hard, but they implement them because it makes the experience better. If something is hard, it just means it will be worked on more. Take a look at explicit sync, it took like 4 years to be rolled out, but it was necessary and got implemented.

I’ll give you point 2.3.1… in general I think KDE looks pretty bad, and gnome is really more polished in many aspects. Unfortunately I really prefer the KDE workflow on big screens (but gnome on laptops).

You mean about adding SSD to gnome, which will not happen?

As an argument in favour, I see:

• Support for more applications that “don’t want” to implement CSD (i.e. foot terminal, davinci resolve, that one archive manager I can’t remember)
• Lifting burden for applications that don’t need custom decoration buttons, and so don’t care about implementing their own decorations
• Making the decorations on those applications consistent with the theming of the system

As an argument against, I personally don’t see any. Sure, most gtk apps are designed for CSD and will not translate well to SSD, but I just don’t see why that should stop gnome from implementing SSD. I remember the gnome maintainers were strongly convinced against SSD, but I don’t remember their argument

Paleo Kabi-Lamius

Ahhh, Verona, the city of Romeo and Juliet, and of trademark infringements

But what about the surname? Grandoni basically means Very Big. The coincidences keep piling up for Mr. Very Big Dino

If you are writing a parser in haskell just use Happy and get it over with

I experience something similar on a vega56, but it doesn’t happen on generic high loads, it happens only

• in some specific loads (for me it was mainly A Plague Tale: Requiem)
• when something touches the grounding of my monitor (the display port of the GPU is faulty, it seems)

goo-goo g’joob, g’goo goo g’joob Goo goo g’joob, g’goo goo g’joob, g’goo.

I would like to interject for a moment. This statement is technically true but disingenuous and facetious.

While it’s true that Linux is just the kernel, what most people refer to as Linux is actually the Operating System GNU/Linux, or, as RMS would now call it, GNU plus Linux, or sometimes, a less GNU depended, but mostly GNU/Linux compatible OS, or, as I have literally just now come to call it */Linux.

Moreover, a modern */Linux system is expected to be based on SystemD, unless explicitly avoiding it due to some technical constraint or some desired feature of another init system. One could come to call this SystemD/Linux.

And lastly, this kind of use case would be the perfect match for a Wayland shell, as opposed to an X11 shell. Which would be more efficient, and would give the shell more freedom in the management of windows.

As a result, when asking about a Linux phone, we could expect one is talking about a phone running a SystemD+Wayland/Linux OS, or at least a mobile-focused */Linux OS.

The Android kernel is a, largely downstream, fork of the Linux kernel, but the Android OS is in almost no way compatible with any */Linux OS, and it’s instead its own completely different OS.