yes
NekkoDroid
joined 2 years ago
IIRC Mono was mostly used for WASM as it was optimized for smaller builds than the full fat CoreCLR (talking about .NET non-Framework Mono)
It really wouldn't change anything in the long run. Any company that creates a browser is gonna need some form of income and people aren't willing to pay for a browser. What would be their incentive to continue to work on the browser when they aren't being paid?
The kernel modules usually are signed with a different key. That key is created at build time and its private key is discarded after the build (and after the modules have been signed) and the kernel uses the public key to validate the modules IIRC. That is how Archlinux enables can somewhat support Secure Boot without the user needing to sign every kernel module or firmware file (it is also the reason why all the kernel packages aren't reproducible).
And technically you can whitelist other certificates, too, but I have no idea how you might do that.
When you enter the UEFI somewhere there will be a Secure Boot section, there there is usually a way to either disable Secure Boot or to change it into "Setup Mode". This "Setup Mode" allows enrolling new keys, I don't know of any programs on Windows that can do it, but sbctl can do it and the systemd-boot bootloader both can enroll your own custom keys.
I did hear that one of their newer versions does use eBPF, but I haven't even remotely looked into it.
I don't think any of the major distros do it currently (some are working twards it tho), but there are ways (primarily/only one I know is with systemd-boot). It invokes one of the boot binaries (usually "Unified Kernel Images") that are marked as "good" or one that still has "tries left" (whichever is newer). A binary that has "tries left" gets that count decremented when the boot is unsuccessful and when it reaches 0 it is marked as "bad" and if it boot successfully it gets marked as "good".
So this system is basically just requires restarting the system on an unsuccessful boot if it isn't done already automatically.
One way to notice a person has "systemd derangement syndrome" is by looking at how they write systemd: if they write it SystemD they are already in late stages of SDS and it isn't curable anymore.
It's not ifn't
Oh I dunno, maybe something with almost 700 comments? (HDR).
If apps don't want to save their state when they close there isn't much a window manager can do about that. The only part the window manager would be involved in is with positioning its window and that is hardly something very critical to the functionality of an app.