3 ms·
> Android is written with deep and casual connections to Google's systems all throughout the codebase. It's like a cockroach infestation. There's no concept of
by zozbot234 6y ago
> Android is written with deep and casual connections to Google's systems all throughout the codebase. It's like a cockroach infestation. There's no concept of anyone potentially not wanting to connect to their services regardless of how trivial the "value add".
Par for the course in embedded development. Tuere are plenty of bad things to be said about AOSP, but it's still way better than any of its Linux-based forerunners. Remember the OpenMoko?
(Of course, this is not to say that further improvement is not possible! So, I might well agree with the gist of your comment from that POV.)
- ThenAsNow 6y ago> Par for the course in embedded development. It may be, but I don't don't see why it must be that way any more than it must be that way on the desktop. At least give me full exposed control over whether and what connections it makes even if the defaults are what they are now!* I can live with that, if there is graceful degradation. Android is not written with the idea that anyone should have that kind of control over their own device. *I get that Google doesn't owe this to anybody, which leads back to the need for a privacy-first/RYF type of phone HW and SW.