> Remind me again why we decided to do all this stuff client side?
I would guess easier reactivity and state management on the client. You don't have to do things the jQuery way in manually having to sync your DOM to your data on changes/api data.
Defaulting to degraded is a bad default. Mounting a btrfs device array degraded is extremely risky, and the device not booting means you'll actually notice and take action.
worth noting Microsoft had a solution a few years ago that would of prevented this issue from happening, Windows 10X, due to atomic updates.
> In Linux, software doesn't even get that option. Nothing ever gets kernel access except the kernel itself. Root is not kernel access.
root has kernel access, even if the kernel restricted it, it can write to the disk and change the boot process.
also worth nothing that a popular form of software distribution on Linux is curl http://randomscript.sh | sudo sh which is arguably worse than anything on Windows.
> Eternal shame on Google for not insisting that Android would follow the "PC model" of the user being root on their own machine and DRM ..
To be fair to Google, banks don't usually allow you to download and generate EMV tokens to perform card transactions on your PC, which places a different set of security requirements (legal requirements too) on Android phones for things like Google Pay to exist.
> Depending on correct glibc, dependencies being installed with the right settings, environment variables,makefiles being compatible with what your system has,having the right kernel version, etc.
Apart from having a bingo at what dependencies you bundle, AppImage makes no effort to actually solve this, where as Flatpak and Snap do. The reason glibc, environmental variables, dependencies is important is because the Linux desktop is not a single distribution etc, nor is there one arbiter keeping ABI stability.
You venture out onto a distribution that is not what the AppImage was built on and you see what a wild ride it is of if things are working or not. Incompatible curl versions, glibc, mesa, etc.
AppImage pretends to work like .exe on Windows, or .app on macOS, but it doesn't share anything similar with them at all. Both Windows and macOS have stable userspaces where things don't change, Linux on the other hand...
For refence, Flatpak solves this via freedesktop runtimes and Snap solves this by installing Ubuntu containers.
Ironically the Alternative Vote system would of likely prevented the Tory parties from having such a bad loss this election (and potentially a majority).
Keir Starmer is a human rights lawyer, would be a bit weird for him to suddenly have no regard for international law where many human rights (ECHR) come from and likely divide his party.
Not saying he's got a backbone, but he's just going for the easier option that keeps his party united.
Microsoft loves pushing people to buy macOS devices it would seem.
Windows really does have the potential to be ideal for professionals, the things macOS does that make it better are all small but Microsoft just seems to paramount on sabotaging their operating system.
I really feel sorry for OEMs that really don't have a choice but to ship Windows and have to stomach this shit being associated with their products.
I would guess easier reactivity and state management on the client. You don't have to do things the jQuery way in manually having to sync your DOM to your data on changes/api data.