- Mar 6, 2017
- 813 (1.97/day)
|System Name||My System|
|Processor||Intel Core i5 3570k @ 4.4 GHz|
|Cooling||ThermalTake Water 2.0|
|Memory||4x4 GB of Corsair Vengeance DDR3-1600|
|Video Card(s)||AMD Radeon R9 380 with 4 GBs of RAM|
|Storage||Samsung 850 EVO 500 GB SSD (https://www.techpowerup.com/ssdz/details/5163/)|
|Display(s)||HP 2311x and Acer G206HQL|
|Audio Device(s)||On-Board Sound|
|Power Supply||Corsair 750 Watt|
|Software||Windows 10 Pro|
That's what you get from a strategy that prioritizes rapid introduction of new "features" at the expense of long term stability. Which is sadly is becoming the trend with most major vendors these days (Looking at you, Microsoft).
Had Google shipped Android with a skinning engine of sorts (think WindowBlinds) you could build your entire UI in XML and have that XML file loaded at boot time thus completely changing the way the whole entire UI is displayed to the user along with an extension system similar to what every single modern web browser has to extend the system. This, unfortunately, wasn't done when Android was released and that's why adding just about anything to Android is a complete pain in the ass. Google desperately needs to build these frameworks so that you can change everything about Android without having to touch core Android code, the moment you touch the core code is the moment you make patching a complete headache.
If you look at how Apple does things with iOS you'll see what I mean. Things like PhoneKit, ARKit, and the various other "kits" that iOS has that allows apps to plug into iOS without having to change core iOS code. Think of all of these "kits" as nothing more than an extension framework that allows apps to do things and plug into the OS. This, from a purely technical standpoint, is superior in every way to having to hack stuff into the core code of the OS. Google has learned this lesson the hard way and you can see this in Android Oreo, though they are baby steps.