People with PhDs in Vim will laugh at this, but I sometimes connect to remote systems through VS Code SSH connections when I’m working on a project with multiple files on a remote system.
From personal experience: if you’re trying to dual-boot with Windows, I recommend using completely separate drives (rather than separate partitions). Windows is very shitty about overwriting your Linux boot partitions when it updates. Having a separate drive isn’t fool-proof, but it helps.
I haven’t needed Windows in >10 years though, so maybe it’s not as shitty about that, but I recommend caution.
Tell that to my eyes when your application only has a blinding light mode. Theming is an accessibility feature and should be prioritized as such.
It’s 2023. Every application should have a theme engine built-in. If not, that’s on the dev. Let’s not make a movement out of a lack of interest in providing support for accessibility.
You can root on GrapheneOS. You do it exactly the same way you’d do it for the stock Google ROM:
Have an unlocked bootloader. Yes, this means that it “”“defeats the purpose of GrapheneOS”“”, if the purpose of GrapheneOS isn’t for you to avoid Google’s privacy nightmare. I use GrapheneOS for privacy moreso than security, and not being able to block ads properly is irritating.
Install the Magisk app.
Extract the boot.img from the GrapheneOS image and patch within Magisk.
Flash the patched boot image in the bootloader.
The main annoyance with this is that you’ll have to do that dance every month when a security patch gets released, but for me, it’s better than vomiting from exposure to ads on mobile.