.png)
Using clocks, multipliers and RAM to compare performance is like comparing the speed of two cars without knowing which ones are thinner, which tires are sprayed.
The iPhone and the iPhone 8 are not out of the norm for technology: Every smartphone in the market is comparable to a competitor. This year, with the leap of three new iPhone models on a six-core chip, the comparison table between the iPhone X, the iPhone 8 with the Galaxy Note8, the LG V30 or other Android tablet models became even more attractive.
But I have to say straight to you: it is a type of "trick" comparison. The numbers are so misleading that you know very well which smartphone is better than any smartphone. The reality is not so simple.
On top of all, the biggest mistake in comparing the configuration of the iPhone and Android phones is that these comparisons ignore the role of the operating system. Anyone who has read through "basic computer" books probably knows that the operating system (and drivers) is the only software layer that has direct access to the hardware. All application / service layers must go through the operating system: no matter your Word application calls directly to the keyboard or printer.
On mobile, with other types of applications, this principle stays the same. In other words, when you ignore the role of the operating system when comparing performance, you miss the core of the user experience.
In this core battle, Android is forced to lose. Because Android is the operating system for all kinds of hardware. Many types of hardware mean that Android must carry more abstract layers than iOS; Each Android hardware can not have the same level of optimization as the iPhone and iPad.
Internal operation of the components is not simple.
Let's talk about RAM first. The more RAM you have, the more cached it is, that's it. But that does not mean that the RAM parameter is the only thing that determines the speed at which the app loads from memory on the main screen. Load the app from the hard drive / internal memory to the RAM, from the RAM to the cache and into the CPU register, which is a very complex process designed by senior engineers. I assure you that most iOS or Android developers are not knowledgeable enough about this process (despite the fact that they should not know).
Not to mention, no manufacturer has unveiled the flash chip speed on their product. Do you understand RAM is "buffer" memory?
The same chip. If the same CPU is Intel, running Windows in the majority of cases, the more multiplied, the higher the pulse will bring more powerful performance. But the CPU is not a simple part - if it is simple, the chip industry has not been called the harshest industry in the world. Perhaps 90% of users have never heard of the concept of "register", which also understands the mechanism of cache operation, does not analyze the difference between 32bit and 64bit, nor does it explain the role of die size. for chip performance.
But manufacturers and marketing companies pack everything into the numbers ahead of GHz and GB.
Those who are knowledgeable about software engineering will understand that they should not care about the complex mechanics of the hardware. As for what Apple or Google + Samsung / HTC / Xiaomi ... bring to them, they have the only way is ... accept the truth and ensure their work is the best. They can only know and accept that the iPhone's multiplier performance is higher than the Galaxy, that the Galaxy has more than the iPhone. All they can do is optimize the best, test it thoroughly for the applications they write on the platform provided by Apple and Google.
Apple understands this very well, so they choose the best path for developers. The first advantage lies in the limited number of hardware options to ensure optimal operating system and reduced test matrix (application volume test). The second benefit lies in the single core: With the end-user application, single-core performance is more important than multi-core performance. Programmers for end-user applications should not bother about threading or threading priorities - they are confusing and very error prone.
If you have concerns about threading: Objective-C manages the flow better than Java on Android.
This year, Apple suddenly increased its CPU multiplier and also acquired its own GPU design. Apple has a very practical reason to do so: iOS 11 comes with the Core ML platform that caters to device-based applications and ARKit enables the creation of the most popular, great. These are the first personal computer areas that actually require multi-core processing: with traditional AIs, software developers who understand the brain should place them in the cloud rather than "stuff" into the device. fish.
Not to stop there, Apple goes a step further in processing the chip: enabling the activation of any number of cores instead of following the big.LITTLE of ARM, which only activates only one of two cores (real Android manufacturers often ... cheat with big.LITTLE when the benchmark is detected).
When Apple does that, Android has no advantage at all. Leaked Benchmark Geekbench shows the single multiplier effect of the high Bionic A11 ... double the Snapdragon 835 on the Galaxy S8. The multi-core performance of the Bionic A11 also surpassed Snapdragon 835 to 2000 points. This overwhelm is evident by both hardware and software, but developers will simply understand that the Android app can not match the iOS app for performance.
And up to the final and most important experience - the user experience, the iOS app always outpses the Android app in terms of download speed. This is the only kind of "power" that you and I can feel. The debate about chips, about RAM, while we do not really understand them; It is pointless to make excuses.
Technicians know that they will only care about their jobs, not worry about modules, functions ... have packaged by others. Technology users should not compare anything but the speed / quality of the experience they receive.
By comparing the configuration to assign to the actual experience speed between iOS and Android is a false comparison. They contribute to a dishonest and dishonest face for the hi-tech industry: instead of focusing on factors that can really improve a user's quality (for example, improving code, hard drive / software ...), the manufacturer is looking to increase a few hundred MHz or cram a few more CPU to "out" superior to the user.
The price difference between the two mid-range and low-end chips, between 2GB and 4GB, is certainly less than $ 30. Investing in product optimization is different: a few million to several billion dollars, not to mention the management issues, human problems ... Stop being "dazzled" by the configuration board. Get rid of them and go to the store to test your dream phone.
The iPhone and the iPhone 8 are not out of the norm for technology: Every smartphone in the market is comparable to a competitor. This year, with the leap of three new iPhone models on a six-core chip, the comparison table between the iPhone X, the iPhone 8 with the Galaxy Note8, the LG V30 or other Android tablet models became even more attractive.
But I have to say straight to you: it is a type of "trick" comparison. The numbers are so misleading that you know very well which smartphone is better than any smartphone. The reality is not so simple.
On top of all, the biggest mistake in comparing the configuration of the iPhone and Android phones is that these comparisons ignore the role of the operating system. Anyone who has read through "basic computer" books probably knows that the operating system (and drivers) is the only software layer that has direct access to the hardware. All application / service layers must go through the operating system: no matter your Word application calls directly to the keyboard or printer.
On mobile, with other types of applications, this principle stays the same. In other words, when you ignore the role of the operating system when comparing performance, you miss the core of the user experience.
In this core battle, Android is forced to lose. Because Android is the operating system for all kinds of hardware. Many types of hardware mean that Android must carry more abstract layers than iOS; Each Android hardware can not have the same level of optimization as the iPhone and iPad.
Internal operation of the components is not simple.
Let's talk about RAM first. The more RAM you have, the more cached it is, that's it. But that does not mean that the RAM parameter is the only thing that determines the speed at which the app loads from memory on the main screen. Load the app from the hard drive / internal memory to the RAM, from the RAM to the cache and into the CPU register, which is a very complex process designed by senior engineers. I assure you that most iOS or Android developers are not knowledgeable enough about this process (despite the fact that they should not know).
Not to mention, no manufacturer has unveiled the flash chip speed on their product. Do you understand RAM is "buffer" memory?
The same chip. If the same CPU is Intel, running Windows in the majority of cases, the more multiplied, the higher the pulse will bring more powerful performance. But the CPU is not a simple part - if it is simple, the chip industry has not been called the harshest industry in the world. Perhaps 90% of users have never heard of the concept of "register", which also understands the mechanism of cache operation, does not analyze the difference between 32bit and 64bit, nor does it explain the role of die size. for chip performance.
But manufacturers and marketing companies pack everything into the numbers ahead of GHz and GB.
Those who are knowledgeable about software engineering will understand that they should not care about the complex mechanics of the hardware. As for what Apple or Google + Samsung / HTC / Xiaomi ... bring to them, they have the only way is ... accept the truth and ensure their work is the best. They can only know and accept that the iPhone's multiplier performance is higher than the Galaxy, that the Galaxy has more than the iPhone. All they can do is optimize the best, test it thoroughly for the applications they write on the platform provided by Apple and Google.
Apple understands this very well, so they choose the best path for developers. The first advantage lies in the limited number of hardware options to ensure optimal operating system and reduced test matrix (application volume test). The second benefit lies in the single core: With the end-user application, single-core performance is more important than multi-core performance. Programmers for end-user applications should not bother about threading or threading priorities - they are confusing and very error prone.
If you have concerns about threading: Objective-C manages the flow better than Java on Android.
This year, Apple suddenly increased its CPU multiplier and also acquired its own GPU design. Apple has a very practical reason to do so: iOS 11 comes with the Core ML platform that caters to device-based applications and ARKit enables the creation of the most popular, great. These are the first personal computer areas that actually require multi-core processing: with traditional AIs, software developers who understand the brain should place them in the cloud rather than "stuff" into the device. fish.
Not to stop there, Apple goes a step further in processing the chip: enabling the activation of any number of cores instead of following the big.LITTLE of ARM, which only activates only one of two cores (real Android manufacturers often ... cheat with big.LITTLE when the benchmark is detected).
When Apple does that, Android has no advantage at all. Leaked Benchmark Geekbench shows the single multiplier effect of the high Bionic A11 ... double the Snapdragon 835 on the Galaxy S8. The multi-core performance of the Bionic A11 also surpassed Snapdragon 835 to 2000 points. This overwhelm is evident by both hardware and software, but developers will simply understand that the Android app can not match the iOS app for performance.
And up to the final and most important experience - the user experience, the iOS app always outpses the Android app in terms of download speed. This is the only kind of "power" that you and I can feel. The debate about chips, about RAM, while we do not really understand them; It is pointless to make excuses.
Technicians know that they will only care about their jobs, not worry about modules, functions ... have packaged by others. Technology users should not compare anything but the speed / quality of the experience they receive.
By comparing the configuration to assign to the actual experience speed between iOS and Android is a false comparison. They contribute to a dishonest and dishonest face for the hi-tech industry: instead of focusing on factors that can really improve a user's quality (for example, improving code, hard drive / software ...), the manufacturer is looking to increase a few hundred MHz or cram a few more CPU to "out" superior to the user.
The price difference between the two mid-range and low-end chips, between 2GB and 4GB, is certainly less than $ 30. Investing in product optimization is different: a few million to several billion dollars, not to mention the management issues, human problems ... Stop being "dazzled" by the configuration board. Get rid of them and go to the store to test your dream phone.
No comments:
Post a Comment