It doesn’t have to. KDE is a great example here. Out of the box, it’s extremely simple to use, as well as familiar in look and feel to Windows. But if you want to - it gives you a lot of customization options. So it doesn’t seem to lose out on anything due to being simplified by default.

And frankly, a lot of Unix software could use a similar approach. I know it’s not that simple, but it helps the users greatly - particularly new ones, but experienced ones too. Perhaps this wave of Windows refugees will in some way lead to progress in this area.

More likely a shift rather than expansion. Graphene said they don’t yet know if they’ll support Pixels beyond 10. Looks like they may focus on the new OEM and drop Pixels.

Not really a ‘Fairphone issue’ and more a general ‘smartphone issue’. The vast majority of OEMs don’t invest into security and just use random parts with mostly stock Android. Sometimes they actually make it worse by replacing AOSP apps with their less secure ones. Which sadly will become more common with Google abandoning AOSP.

Fairphone simply isn’t focused on security. Should that change? Are Fairphone users interested in improved security?

The USA with its corporations setting a new, unbeatable WR in any% glitchless turning into a dictatorship with zero human rights or freedoms.

Judges should be using ouija boards to communicate with people killed by death penalty. “So you were guilty, right?” To make sure everyone gets a chance to appeal the decision.

One of the most cozy setups I’ve ever seen. Except whatever it is surrounding the cable in the top right. Kinda disgsuting looking.

Good point. Sometimes it helps to read properly

no more locked bootloader

Likewise modifying the bootloader requires unlocking it - which means no more secure boot and anyone who takes your phone can happily boot whatever they like on it. This is also bad.

Except for Graphene. The last step in the installation is locking the bootloader back, and the phone clearly says it’s locked.

You’re also massively wrong about DirectX on Linux, DXVK and VKD3D both work to run various versions of it on Linux.

I very clearly wrote that Linux does not support DirectX. Which is 100% true, no matter how you look at it. Just because there are translation layers, it doesn’t mean Linux ‘supports DirectX’, because it doesn’t. It supports Vulkan, which DXVK and VKD3D translate DirectX API calls to.

Let’s say you can’t read Spanish, but you hire a translator to translate a text for you. Now you can read it. Does that mean you can suddenly read Spanish?

They created the Game Porting Toolkit a while ago

Hmm… Must have missed that. I’ll need to take a look. Might be the exact same thing I mentioned and I just had no idea it was already released.

The RaspberryPi has existed for ~15 years at this point, the platform is far more mature than Windows on ARM and rivals macOS for support.

I wrote “From my experience” and “Might depend on the device though.” Also, RaspberryPi is not a daily use device. At least not for the vast majority of people.

If Linux works on ARM for other people - great. I’m hoping to be able to switch to it sometime in the near future. However, the last time I tried it was horrendous. A lot of programs I use were completely unavailable, with no compatibility layer that I know of. That was about 2 years ago.

That said, I also tried Windows 11 on ARM around the same time and it was great. Practically everything worked out of the box and worked flawlessly. It was basically the same experience as on amd64.

After introducing Metal (their own proprietary graphics api), Apple killed OpenGL support and never implemented Vulkan support. Almost every single video game nowadays uses either DirectX (Microsoft’s proprietary API) or Vulkan for 3D graphics. 2D games use OpenGL and Vulkan. OpenGL and Vulkan are both open source and cross platform.

Windows supports everything, Linux everything except DirectX, and MacOS (for Apple Silicon devices) only supports Metal. You can still play OpenGL games on Intel-based Macs. Steam tells you which games won’t work on recent Mac systems.

In order for a game to run on ARM Macs, it has to either be ported to Metal, or there needs to be a compatibility layer like Wine and Proton. However, neither of these two work, since Apple no longer supports OpenGL or Vulkan. Theoretically, it is possible for people to write a new compatibility layer, specifically for Metal. The problem is, nobody wants to, because it’s a lot of work (as usual with development for Apple devices), and you never know when Apple may decide to drop support for some other libraries/APIs/drivers.

Additionally, Apple seems to be working on their own Metal translation layer. Leaks show impressive performance in Cyberpunk 2077. However, nobody knows what the availability will be like or when it releases.

In the case of Macs it’s not an issue with the ARM architecture, but with Apple. Since they dropped support for some libraries a few years ago, new versions of wine (and proton) stopped working on Apple Silicon. That’s the main and pretty much only reason why you can only play like 13 games on newer Macs.

As for Linux, ARM support is still in its early stages. From my experience it’s not even ready for regular daily use. Might depend on the device though. M1 Macbooks run pretty good with Asahi.