- Joined
- Mar 6, 2017
- Messages
- 3,209 (1.23/day)
- Location
- North East Ohio, USA
System Name | My Ryzen 7 7700X Super Computer |
---|---|
Processor | AMD Ryzen 7 7700X |
Motherboard | Gigabyte B650 Aorus Elite AX |
Cooling | DeepCool AK620 with Arctic Silver 5 |
Memory | 2x16GB G.Skill Trident Z5 NEO DDR5 EXPO (CL30) |
Video Card(s) | XFX AMD Radeon RX 7900 GRE |
Storage | Samsung 980 EVO 1 TB NVMe SSD (System Drive), Samsung 970 EVO 500 GB NVMe SSD (Game Drive) |
Display(s) | Acer Nitro XV272U (DisplayPort) and Acer Nitro XV270U (DisplayPort) |
Case | Lian Li LANCOOL II MESH C |
Audio Device(s) | On-Board Sound / Sony WH-XB910N Bluetooth Headphones |
Power Supply | MSI A850GF |
Mouse | Logitech M705 |
Keyboard | Steelseries |
Software | Windows 11 Pro 64-bit |
Benchmark Scores | https://valid.x86.fr/liwjs3 |
It also comes from the fact that in Android there's no real API framework to plug stuff into the system with. As I stated before with Windows, if you want to add something to Windows all you need to do is add a DLL or add some stuff to the Registry and you are done. From a purely technical point of view Windows is superior in every way to other operating systems because it allows for a lot of customization without having to do anything with core code. Even the driver framework of Windows is superior to Linux because drivers aren't part of the kernel, they're loaded into kernel-space at kernel initialization time. This of course make it so that drivers that were for Windows 7 can (in theory) work in Windows 10. This is brought about by what is sometimes referred to as an ABI or Application Binary Interface, Linux does not have one.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.
Last edited: