Earlier quoted context omitted.
Sure. But for South Korea and Japan it's less so; those nations already take a national security posture that leaves them exposed if the US were to turn against them.
South Korea and Japan have been allies of the US for quite a long time and have zero reason to think that would ever change.
The Huawei Disaster Reveals Google’s Iron Grip on Android
181–190 of 355 posts
Re: The Huawei Disaster Reveals Google’s Iron Grip on Android
#182Re: The Huawei Disaster Reveals Google’s Iron Grip on Android
#183Earlier quoted context omitted.
That's interesting. Do you have any more info on where they are putting those factories?
Everywhere from Nigeria to Lesotho basically. https://www.goodreads.com/book/show/35288650-the-next-factor...
If you build a factory there, you have to also build the power plant, the roads or rails, train and educate the workforce, and secure everything.
Contrast that against somewhere like Indonesia, where you have literacy rates of 95%, decent infrastructure, and average IQ of 87.
On top of all that, the 'best' workers in Africa, which could be your foremen or managers, are usually already comfortably employed directly or indirectly thanks to foreign aid.
If Africa truly wants development, they should just lease out huge tracts of land to the Chinese for 200 years, and give them authority over it all.
Re: The Huawei Disaster Reveals Google’s Iron Grip on Android
#184Re: The Huawei Disaster Reveals Google’s Iron Grip on Android
#185We already know this, which is why we want a free platform based on AOSP and replacements for Google services.
... or just a Free platform that doesn't have a malware-able god process called zygote and all those insane layers of abstraction Android has.
What?
Re: The Huawei Disaster Reveals Google’s Iron Grip on Android
#186Earlier quoted context omitted.
Isn’t Android open source? So why can’t Huawei simply fork it?
Google has spent the last decade cutting apart the open part of Android and making it more and more proprietary. Launcher, Phone app, Messages, Contacts, Calendar. All proprietary. Notification API, Location API, SMS APIs and step counter APIs, and even the new app format. All proprietary. It's a huge undertaking building an app for Android today without using Google's services, and sometimes even impossible. If you…
Note too that they could have gone the Microsoft IE route and declared various apps as part of the OS. Instead they made their apps separate from Android, and let them succeed by bundling them together. Amazon Fire is at least one example where the Play Store et al. are not installed.
Re: The Huawei Disaster Reveals Google’s Iron Grip on Android
#187Earlier quoted context omitted.
Google has spent the last decade cutting apart the open part of Android and making it more and more proprietary. Launcher, Phone app, Messages, Contacts, Calendar. All proprietary. Notification API, Location API, SMS APIs and step counter APIs, and even the new app format. All proprietary. It's a huge undertaking building an app for Android today without using Google's services, and sometimes even impossible. If you…
Phone companies tried to replace the open versions first. Google was faced with either: a different version of Android on each phone (with the apps replaced,) or making their own versions. Note too that they could have gone the Microsoft IE route and declared various apps as part of the OS. Instead they made their apps separate from Android, and let them succeed by bundling them together. Amazon Fire is at least one…
No, their action actually lead to this in the first place — previously, each manufacturer slightly modified the AOSP apps, now each manufacturer actually builds their entirely custom apps for this purpose, as most can’t or don’t want to license Google’s apps for that purpose (they license the base Google Play apps, but e.g. not messages or the phone app or the launcher).
Re: The Huawei Disaster Reveals Google’s Iron Grip on Android
#188Earlier quoted context omitted.
> Google has spent the last decade cutting apart the open part of Android and making it more and more proprietary. Replacing those bits is still less work than writing your own entire OS. There are even open source projects to replace those bits.
Yes, microG exists and is amazing — but even it is only replacing an absolutely tiny part of the APIs, and even those it can’t replace fully yet and a lot of work is still to be done. I remember days when Android was still open, nowadays I’m fighting against the ever-increasing restrictions with my open source apps with every single OS update.
They're saying that there's easy and simple drop in replacements, app and service wise that can hook into better services/ones you host.
Re: The Huawei Disaster Reveals Google’s Iron Grip on Android
#189Earlier quoted context omitted.
Google has spent the last decade cutting apart the open part of Android and making it more and more proprietary. Launcher, Phone app, Messages, Contacts, Calendar. All proprietary. Notification API, Location API, SMS APIs and step counter APIs, and even the new app format. All proprietary. It's a huge undertaking building an app for Android today without using Google's services, and sometimes even impossible. If you…
> Google has spent the last decade cutting apart the open part of Android and making it more and more proprietary. Replacing those bits is still less work than writing your own entire OS. There are even open source projects to replace those bits.
Re: The Huawei Disaster Reveals Google’s Iron Grip on Android
#190Earlier quoted context omitted.
The play store is not the sole way to distribute apps. You can download the .apk files, or get them by mail, or use another play store that has the same apps. The play store is just a repository of some apps.
I believe the Play store is treated 'special' though - F-Droid can't install apps in the same way unless you're rooted and install the priv-app.