Yeah, I think that comes from the developer having high standards for hardware security. The effort put in is a waste if the hardware fails. I would have thought Samsung would have been suitable too, though.
What about /e/OS or plain old degoogled Lineage? I like it as a phone OS, it's just a shame the app ecosystem is so dependent on Google's services.
I can anecdotally say that the more right-leaning people I know are the most anti-FOSS but I'm not sure that applies generally.
Even that comes with a caveat: the people I know disagree with it philosophically, i.e. they can't see how it can work for the maintainer and won't donate, yet are as happy as anyone to use something for free.
Just wanted to add a bit about Proton since you mentioned it and I use it quite heavily.
Pros:
All-in-one platform for storage, mail, VPN, password manager and calendar. Usually works out cheaper than multiple providers.
E-mail aliases built-in to the password manager makes it a breeze to manage. (Tutanota also supports aliases.)
Personally, I think the UI is more polished. Not important for privacy but it's a plus for the non tech-savvy.
Cons:
All-in-one platform. I'm acutely aware that I'm going to have a headache if Proton is enshittified.
If you're not looking for all of the products they offer, it's just expensive. Tutanota is cheaper for e-mail alone.
The Drive app needs improvement. Migrating my files was painful and I want automatic Camera uploads. You might be okay with the Windows desktop app.
The Calendar app has issues when not connected to the internet.
The password manager doesn't have a desktop application and managing it through the browser extension or app isn't great.
No subject-line encryption support (and other PGP interoperability issues on the free version) but... unfortunately, I don't get many PGP encrypted e-mails anyway.
Otherwise these two are largely like-for-like for e-mail. There's no benefit to Proton being hosted in Switzerland and I didn't move to be warrant-proof or anything silly. The idea is really just moving emails away from an advertising company and paying for a quality service.
Yeah, this is one of those things which sounds great on paper but also introduces problems. I've seen people get really annoyed when exception messages are translated because it makes them harder to search for online. That would need to be solved too.
I've had huge issues collaborating on a spreadsheet with a Spanish client. It tries to open the sheet in your locale and then can't find the functions. Insane that Microsoft didn't even add some metadata to allow me to work on it in Spanish.
Exactly. I used PHP for years, I haven't "not used it." It was the first programming language I seriously learned. Writing good code was tedious if not impossible and that became even more obvious as I expanded to C#, Java, Python and C++; none of which tolerated any of the bad and unconventional practices I'd inevitably picked up. Keep in mind, I was actively trying to avoid bad practices and pay close attention to types but still got kicked to the curb hard when I tried other languages. I haven't had that since.
I appreciate it's changed since, I'm happy to see it's not the same dumpster fire it once was, I also don't care. I don't actively trash it, I just think there's usually a better option.
I need to get into NixOS but I have a similar variation on servers: ansible for state of systems, Borg + Borgbase for data (kept in /srv) and code (including ansible) are in Git.
The separation between data and state is really great. You want to be able to go from a base install and only bring in everything which makes your setup different.
Yep, it's usually an existing idea with progression in a few areas. You could definitely achieve serverless with a cluster of servers hosting the same scripts in cgi-bin and I think that context helps to put it into perspective.
I think it's a maturity thing. You eventually see so many trends come and go, peaks and troughs of hype cycles and some developers (probably including yourself at least once!) overusing certain new tech.
You eventually discover what works with current tech and then you can become healthily critical of anything new. You see it more for where it can fit and where it can't.
If you have something small and stateless then serverless is easy and, more importantly, scalable. It was a little easier to see its role once the hype fog had lifted and I had a problem to solve with it.
I'd be pulled up at my job for any PR exceeding a few hundred lines. I don't even know what they'd do if I just dropped a 15000 line stinker.