What is the most disgusting thing about android?

I don't want to mention anything. the most disgusting thing is that it will start several programs and background services that I don't even need for various reasons without knowing it. Sometimes it is even incredible, then these processes are still there.

The android memory management method is called low memory killer. This is simple and cannot be simple. It just keeps 30 mb of buffer. You can start a new program and put it in this 30M, at the same time, it clears 30 M; that is to say, it ends the program that it feels useless at this time.

There is a core idea here, that is, the memory I buy is not used for free. To ensure that more programs are in the memory, the probability of switching to these programs is higher, and the winning speed will be faster.

This may sound correct, but it is not easy to handle, that is, the end of an old scalpers like android: You don't know when the CPU or memory will be occupied by others, as a result, it is obvious that it is not smooth intermittently. It is a pity that Google cannot handle this problem, and it is easy to make a fuss over the boundary of this buffer.

Take a closer look at the architecture of the Java program in android and you will know that sometimes you only need a simple action, but at this time, a lot of memory is involved. I don't know whether this depends on the object-oriented organization method or Google's design.

On the other hand, it is difficult to constrain developers with such a design. Take a Process Monitor and take a look at it carefully. In many cases, there is no need to relate many different modules of the software, unreasonable function distribution, especially if these programs are used as Framework extensions and expand around common function sets, such as vendor-defined things, they will be finished.

This is why the Sense interface and native Android have such a big difference in light-weight space-free memory usage (HTC's primary designer should open it ), and why Android is incredibly slow (compared with other vendors.

Let's observe settings.apk again. What does this stuff have? Actually it takes several MB of memory. For God horse for God horse this is for God horse! Programs that can be quickly loaded and started, or a part of the program, do not have to stay in the memory. We can say that Google's resident memory strategy will eventually offer discounts on things that are invisible to non-resident memory users.

What is the other reason that affects the speed? These are the damn services: although Google seems to want to plan this, at least for the moment, these services will regularly compete with the user's current operations to grab CPU resources.

Let's take a look at the Linux kernel programming to handle this problem: the interrupted routine must end as quickly as possible, and the big job should be handed over to a queue. Linux Kernel programmers all understand this, but Google does not have the right to require us to make applications like drivers. What's more, the quality of the entire runtime design makes it harder for developers to handle this problem than in the kernel!

(Android's primary designer should be removed. Do you know what you designed ?)

I don't know whether the competition will be like this. If one of them is willing to work hard, Android will surely be finished, whether it was 3.5 or 9.0 at that time. Because the rationalization of large-scale changes to the runtime is equivalent to directly reducing the number of apps back to prehistoric times.

But it's hard to say that, from the top to the bottom, from the largest to the smallest, the world has changed, and the hearts of the people have changed. Buddy, I have to pay attention to these aspects to find opportunities. One day I am financially free. I would rather go back to a product that would never endure such a problem.

 

P.S. Once there is real competition, rather than several oligarchy, it is not impossible for the war to reach the PC platform. At that time, the first drop in sales revenue was poor Intel, because we found that there was a free lunch, and downloading a pirated XYZ would double the experience... (This article is about experience and does not involve real execution efficiency. Although Google is a newbie compared with its competitors in this regard)