It got this way because 99% of people are happy running what's in the app store, and the security protections are more valuable than being able to run arbitrary code.
Linux as an answer doesn't address the needs of 99% of people, so 98% will never adopt it. It's better to meet people where they're at and push for sideloading and alternative app stores.
There are plenty of smartphone companies locking down their bootloaders, but there are others that will let you unlock your bootloader by just running the basic command.
A much bigger problem for running Linux on phones is that standard Linux runs like crap on phones. It doesn't have the mainline driver support amd64 computers have, and the battery life optimizations that make Android usable need to be reimplemented on top of Linux to get a day's worth of use out of your phone. Unfortunately, most Linux applications are written for desktops where they expect the CPU to be running all the time, the WiFi to be accessible whenever they want, and for sleep/suspend to be extremely incidental rather than every two minutes.
Only as long as Google doesn't force Web Environment Integrity through. Running a custom OS won't help if important websites refuse to load unless they're running in an approved browser with a set of approved extensions, on an approved OS, on top of approved hardware.
I've been beating the drum that we need mobile drivers licenses and pairwise pseudonyms. It is a path to beating spam and bots in a way that doesn't hand control over to private entities.
Some folks don't like digital identity controlled by government, but it seems like the alternative is digital identity controlled by oligopoly.
Snopes has this as mixed because Stalin may or may not have expressed this sentiment at some point, but it seems impossibly unlikely to me that this pun works in Russian as it does in English.
This Jupyter (CRDT-based) extension appears to solve the BIGGEST HEADACHE I personally have with Jupyter(lab). Jupyter notebooks allow me to hack code/parameters too fluently, and I can't recover earlier positions in code/parameter space that produced interesting results.
Jupytext and git goes some way towards fixing that, but I don't save to git after every cut/paste of a parameter. This extension is effortless.
As a bonus, the extension appears to allow SubEthaEdit/GoogleDocs style collaboration too. (I haven't personally used that yet.)
I am not a keyboard warrior who got caught up in the nonsense, but I think some people were simply annoyed at adding syntactic sugar for very marginal benefit. “There should be one way to do things” mantra.
I have a long list of grievances with Python, but the walrus situation would never crack my top ten. Put effort into removing cruft from the standard library, make typing better, have the PSF take a stance on packaging. Anything else feels a better use of time.
Whatever, it won. I will never use it, but when I see it will have to scratch my head and lookup the syntax rules.
It was against many people's aesthetic sense. Including mine. But in theory it can be ignored completely, and in practice it is barely ever used (and indeed nobody forces you to add more uses).
Maybe. He was on the BLACKER VPN project for high-assurance, secure VPN. It had strong requirements for configuration management. Larry Wall was a smart, but lazy, programmer that tired of tedious administration. So, he wrote Perl to automate that.
Maybe he did some kind of deep, programming design. It just sounded in that account more like he threw together whatever solved his problem with some nice ideas baked in. Again, that's if it was true that he invented it to automate tedium during BLACKER VPN.
For public examples of A1, look up SCOMP, GEMSOS, and VAX Security Kernel (VMM). Those papers describe the assurance activities required for A1 certification. At the time, due to bootstrapping requirement, tools like Configuration Management didn't have to be A1. People used all kinds of stuff, like Wall building Perl.
While the functional form of the statistical distributions themselves might still be valid, certainly the old parameters are no longer so.