Systemd was actually a “clone” of apple’s launchd. Similarities with windows arise from the fact that it makes sense to manage services in certain ways on modern OSs. Also services on windows are completely different from Linux and MacOS, they are even a different executable file format, not a normal exe.

I can’t. Proton-experimental specific is required for the game to run without disabling dx12 which will lower performance. With proton-ge the game crashes instantly

The only “problem” is that it’s not making 60 fps even in the benchmark. Which is fine, it’s a heavy game, but I would be bummed if it was due to proton overhead and not due to my gpu

Mine is: I don’t really listen to music

Me:

1. make the snapshot after the system is already broken
2. Break it more
3. Don’t restore the snapshot because its old and you can fix it

I already use the fan made launcher for textures, but I don’t need more than 62. I’m getting 30 fps when physx is enabled.

I will try to run the winetrick manually, I expected heroic to do that itself as it does for other tricks.

surface flinger has some X11 code

Does it? I don’t know for sure, but I’m extremely skeptical. Can you point to the source of this claim?

Not entirely, for example you don’t expect the package manager to remove the gnome folder from the .local of every user

They could be using different package managers or different repos

To me the problem is actually removing the old one. You can easily uninstall gnome, but it will leave behind config files and various data. It’s less clean.

Also, there’s an overlap in the libraries required by DEs, so you should use the “replace” option in you package manager (if it has one) to let o t figure out the best way to uninstall one and install the other.

Home is pretty useful actually, just like end. Ins can go fuck itself

Did they have Nvidia? Interesting, didn’t know

Most features missing right now (not all) are against the Wayland philosophy, this doesn’t mean that you won’t get anything but that it needs a “modern era replacement”. Though applications will need to support the replacement. This is usually for good reasons.

The prime example is screen recording. Allowing any program to read and write the entire screen is objectively wrong, no matter what the big time X11 fans say. But there is a replacement: pipewire. Pipewire is extremely advanced and featureful, and it’s more secure because it allows the system and the user to audit who is reading the screen and what part. The problem is that programs need to support pipewire for screen recording, but the main culprits are niche screen recorders (OBS is the best anyway, and it supports it) and proprietary video call software like discord (zoom supports it), which is silly because for electron apps it’s literally a matter of using a version less than 3 years old an adding a flag.

Obviously that’s not true… like, at all…

Android phones use Surface Flinger, which is a compositor that has nothing to do with either Wayland or X11. But we could say it’s kinda similar to Wayland in the fact that it’s composited and uses something similar to GBM and GEMM for managing buffers.

Android drivers don’t even use the same “semantics” as Linux drivers (android uses explicit sync, while Linux is implicit, but they are working on supporting explicit sync because Nvidia and because it’s better). It’s only in the last few years that you can use Linux drivers in android, plus some synchronization stuff.

There’s the Nvidia Shield tablet and some old Google Nexus that runs on tegra. Also if you are one of the unlucky People that bought a Windows RT tablet expecting it to run any program at all, you might have a tegra. Also the Nintendo Switch has one.

Fun fact: if I’m not mistaken, the Nexuses used nouveau.

that makes no sense - you need the key

But if it’s stored in a keyring or similar (like on windows) and the client reads from it you don’t need the file with the plain text key. Like you don’t store the git credentials in a file, but with libsecret.

I would prefer something that never ask for the password.

Things like the gnome-keyring or kwallet keep all the passwords in an encrypted file, they get decrypted and kept in ram using your login password when you log into gnome/KDE session and programs can ask for passwords using some API. Once you log out the passwords are removed from ram and no one can read them. My goal is to have something like this, so I’m never asked for a password, I just log into my session and everything is available

It’s not a solution.

Example: there’s another user with sudo access, he has access to my home folder, encrypting the drive doesn’t solve anything. Or maybe you just are not the system administrator.

It’s not my usecase, but it’s definitely a reasonable situation.

I think it’s only important to Apple, it’s not beneficial to anyone else

Which is bullshit because DRM doesn’t effectively prevent ripping (source: you can find pirated hd content). So it’s literally only harmful to the customer.

I’ll give you a quick demo of how DRM is literally useless at protecting content:

• You need:
  • a machine with any Nvidia GPU series 600 or newer running Windows, a browser with DRM support (e.g. chrome), and optionally sunshine. This is not an uncommon setup
  • any other machine that can run moonlight (even a phone).\
• Services often use widevine as DRM provider, so using the Nvidia machine visit this test page and make sure DRM is working
• Normally the DRM api ensure that the decrypted content of that video can never in any form get out of a special GPU buffer, not even the browser can access it
• enable sunshine on the machine
• Connect from the second machine to the using moonlight and notice that the video is not being shared. DRM seems to be working correctly.
• Now disable sunshine and enable Nvidia gamestream from GeForce experience, and set it up to share the whole desktop
• connect from the second machine to the first using moonlight
• now the video is being shared to the second machine, and DRM is circumvented. There is literally nothing preventing you from recording the screen on the second machine

Now, this is a terrible way of ripping content, it causes at least one reencoding, which reduces quality (a lot of people won’t even notice it), but it is a stupidly simple working demo of DRM circumvention.

Btw, that procedure is not the result of some study, reverse engineering, or any clever stuff. I was literally playing a game in streaming and I went “hmm, I wonder what would happen if I streamed widevine” and it just worked.

As the video points out, a lot of the work in xorg (and Linux in general, fwiw) is done by red hat engineers. So red hat cutting on that investment bears direct consequences for everyone else. Unless of course someone steps up and takes their place in maintenance, but it’s not gonna happen, which is literally why Wayland (and not some revamped xorg) is the future of Linux desktop.

Also, red hat’s decisions often trickle down on most other distros. E.g.: systemd, pulseaudio, pipewire, gnome, not including proprietary codecs, etc.

So, they technically don’t arbiter, but they definitely set the pace.