Topperware

Unfortunately it requires vulkan (it says 1.3, but because vulkan is based on extensions so it probably doesn’t require the full 1.3). So if you have the Intel GMA 950 that’s in the motherboard for your Pentium 4 HT is not supported. But I’m confident that an AMD HD 6000 from 2010 with the Mesa driver “terakan” is enough to run it. And theoretically one could implement vulkan even for an HD 2000 from 2007, but it’s an unreasonable effort.

If they made an opengl backend, you would be golden, as the Mesa driver i915 implements opengl 2.1 for the GMA 950, and it’s definitely enough to run an editor

P.s.: and I sure did not spend the last 30 minutes looking up vulkan hardware

You forgot the part where TeX was created by a CS professor because he didn’t like how his editor printed the formulas in his book

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.

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

If you believe “fat” is a slur, how the hell do you come up with the word “fattist”? Do you also say faggist, jewist and niggist?

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.

Did they have Nvidia? Interesting, didn’t know

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.

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.

That’s weird because it’s against the law.

A recent (few months ago) EU law mandates that if your platform is big enough (in the EU market) to gatekeep users from using other platforms, then it must interoperate with competing services. That means you should thrive because you make a better product, and not because it has more users.

The fine is a considerable percentage of the company’s earnings, that supposedly even the likes of Amazon and Google cannot overlook.

This includes Whatsapp that in a few months will have to be interoperable with competing services like telegram. This requires a protocol, the IETF is working on that. Google probably wishes to use RCS, but Matrix is also working with the IETF.

Apple says iMessage is not that widespread in the EU and should not be included, Google says it is and should be regulated, that’s because this regulation will most likely have effects even outside the EU.

If it’s the flatpak version, try the package manager one. The one on flathub didn’t integrate very well and only really worked for steam games.

Fedora users waiting 6 hours just for the update process

But he’s using a model M, not a symbolics space cadet. Totally inaccurate

What you are looking for is called specialization.

It is currently unstable and incomplete, which means you can activate it by adding the macros #![feature(specialization)] and #![allow(incomplete_features)] at the beginning of the file. But you have no guarantee that it will work the same way on the next version of rust.