He isn’t but all the losers who follow him and gave him money are. I’m surprised he doesn’t face charges of fraud for some of that stuff.

Andrew Tate is facing something like 42 charges at the moment and his brother another 17. For things like rape, human trafficking, possession of indecent images of children. Assuming these pieces of shit are deported they’re likely to be in prison for a substantial period of time. Wouldn’t be surprised if they’re held without bail before the trial which could take a year and then get to enjoy lengthy sentences after it.

This boils down to a Linux using a file system which allows files to be deleted or replaced in the inode table while something has the old file open. So it’s easier (although not simple) to replace packages while other stuff is running. Whereas Windows has to shut everything else down so nothing has the file open to replace it and also fix stragglers during the next reboot.

Stuff like ydotool, wtype exist and presumably there are others for this. Search on automation testing on Wayland and see.

Since it is a niche I’m not surprised if it wasn’t a critical path for Wayland adoption but clearly there are solutions that work for certain compositors and I assume people working on a more robust solution. But allowing one piece of software to sniff or inject input, or capture its content is an obvious security flaw and Wayland devs are right to put it front and centre. If a desktop is to allow those things then it should be through a security model instead of in the absence of one.

Wayland enforces security to stop one process sniffing or injecting input into another. X11 basically has zero security boundaries. So certain things are easier in X11, but then again the price to pay is too much.

So things like virtual mouse positioning, autohotkey, screen capture are harder to do but not insurmountable. It requires protocols that the client / desktop understand and which are fit for purpose. Big desktops like GNOME & KDE Plasma do support xdg-desktop-portal which allows hotkeys to be registered with the desktop, and could potentially be what you need.

The only thing I didn’t like about systemd was the unfamiliarity of the commands. Typing systemctl and a verb and a service and some more arguments feels a bit clunky.

But otherwise it all seems to make sense to me - lots of little services running with least privilege, very simple description of services in unitary files, secure binary logging with proper filtering, proper utilisation of cgroups to reliably kill processes and enforce limits, parallel startup/shutdown etc.

Most of the objections I’ve see to it online seem miss the point and ignore answers which would solve or refute their objections.

It’s like the Amish but with operating systems. Technology has advanced this far but must advance no further.

Systemd and Wayland have become ragebait for some people.

The best I can say about KDE is they’re not as bad as they once were. But even today the KDE human interface guidelines essentially say “do not hide options or move them to advanced dialogs”. It’s no wonder that KDE Plasma is dogshit from a usability standpoint even when it mimics Windows. There is nobody at the wheel controlling it and it shows.

Microsoft put their software in front of people who want to use it to do stuff. They ask them to copy a file, launch a program, select something and copy/paste etc. and they observe their reactions, how long it takes them to find & do the thing. Then they focus on where the people had issues and try to simplify the flow, rinse and repeat.

I would never say Microsoft puts in as much effort to UX as Apple, they still put a fuck tonne more in than any Linux dist. Even GNOME. And the KDE desktop is a dog’s dinner despite basically copying Windows and trying to play the same tune without understanding the notes.

As much as people hate on Windows, Microsoft very clearly put their software in front of people to learn where the pain points are and fix them. Maybe Linux desktops should do likewise because some of them are a usability joke and it hurts uptake. I was playing around with Ubuntu 26.x with KDE last night and there is so much noise and grit in the UI I wonder what is going on with it.

What porn did they take with them?

I think Linux has progressed a lot since 2005. It’s mostly idiot proof these days - it asks about language/keyboard/timezone/wifi and unless you ask for an advanced install (to partition a hard drive or whatever) it just installs.

I don’t think installing Windows is any harder but it may stop to ask for a registration key. Windows also prefers to connect to wifi during installation to fetch patches whereas Linux tends to do it after the fact.

Unless you’re installing some weird corporate build of Windows you’ll have a very simple installation process. Linux has caught up a lot to that experience.

Every operating system contributed to the bloat. Windows has Win32, OS X has Carbon / Cocoa, Linux has X11 and various widget libs that sit on top of it. So it has been a perennial nut to crack to make cross platform widgets - wxWidgets, QT, SWT/JWT/Swing on Java, XMLShell (Firefox), Electron, GTK/GTK#, winelib etc.

Throw mobile platforms into the mix and it’s an unholy mess. Lowest common denominator is HTML and so the likes of Electron “wins” even though it’s bloated and slow.

I still think the web would have been better off if certificates were signed and part of a web of trust like in GPG/PGP. It wouldn’t stop sites from using trusted CAs to increase their trust levels with browsers, but it would mean that tiny websites wouldn’t need to go through layers of mandatory bullshit and inconvenience. Also means that key signers could have meaningful business relationships rather than being some random CA that nobody has a clue about.

I think the main thing holding Wayland back are older drivers which don’t work well with it and impact on things like games. Once its over that hump there isn’t much reason for maintainers to suffer two back ends any more.

You think if they used another licence it would be any different? Countless open source projects have a GPLv3 + proprietary licence which is way more evil than Apache - they poison the open source with GPLv3 so no competitor can contribute without revealing their changes while they themselves can use the proprietary licence. e.g. Trolltech and QT for example but there are many others.

And frankly you should be blessed that you have a fully fledged, open source phone OS you may fork and build from. The OP wants a Linux phone OS and AOSP is a Linux phone OS. There are many forks of Android, closed and open that wouldn’t exist if Google had just decided to be proprietary from the get go. They were under no compulsion to do this but they did. If you have used LineageOS, or GrapheneOS for example then you are a beneficiary of this. You are completely at liberty to have a de-Googled modern phone OS powered by Linux right now.

Wait… they opened it so they can close it?

Android is Linux. It uses a Linux kernel paired with a BSD based user land. Also there is an AOSP version of Android which is Android without all the Google bits. LineageOS and some other security oriented firmwares derive from it. That isn’t to say Google are necessarily happy about this entirely but at the same time, they open sourced most of Android and probably see it as a useful antitrust defence and the impact of flashed devices barely more than background noise.

The issue of bootloaders is an orthogonal matter since Linux or not does not mean bootloader or not - many black box devices use Linux but you won’t be flashing them any time soon - TVs, set top boxes etc. I would argue that regardless of OS, there should be a right to repair law (e.g. in Europe) that allows people to maintain devices beyond their warranty. And if Samsung et al don’t want to do it, then they should have an obligation to unlock devices upon request.