(Zookeeper) Oooo (OO)

Abstract
Excessive object-orientation is a kind of illness that occurs to programmers who use objects over the years. Finally, the original includes poor programming languages and non-essential programming languages, as well as fellow students.

Introduction
Auto scaling from http://www.oreilly.com.tw/column_sleepless.php? Id = j016

Single Word: oooo (obsessive-object-orientation obliquity)
Sound: KK: [O 'ooo] DJ:/o 'ooo/
Solution: N. [Computer Science] excessive object-orientation is a symptom of excessive object-orientation, it occurs to year-round programmers. Finally, the original includes poor programming languages and non-essential programming languages, as well as fellow students.
Example:

1. OO advocates tend to be oooo patients. (OO patients can easily become oooo patients .)
2. People with a good understanding of computer science can get rid of oooo .)
3. Most oo experts used to be oooo victims. (most oo entrepreneurs were victims of oooo .)

When I found out the word Oooo, I also specifically tested the mental disorder (obsessive-compulsive disorder ), I originally wanted to call it obsessive-object-orientation disorder (oood), but I do not like to use disorder at the end of this word, I replaced disorder with the single word obliquity on the start of O, so that the words of the four-member o can be formed.
Today, oooo has a large number of infected people, and the number of others has been forced to rely on others to make a fortune. They often have heavy fantasies that the most amazing thing in the world is Oo, and the opening and opening interfaces all over the world are oo. When programming, they only use large amounts of OO, it does not care about the hidden shadows brought by oo.
The common cause of oooo is that many organizations have their own resources. For example, the following statements can be seen in many regions:
It is natural to show an object. It is easier to teach a child an object than to teach a computer professor, because the professor is already familiar with the operation in e-commerce, he is more familiar with establishing a correct Object Concept.
The above statements are not correct, but many people believe that such statements are correct. I think this theory is due:

1. As long as you know nothing about the principles of the electronic operation, it is very difficult to really learn Oo, because Oo is actually used on the TV. Many people can only understand the issue, but cannot fully grasp the commitment. It is more subtle for multiple types.
2. As long as you know nothing about the principle of the operation of electricity, the defined Oo is not practical. It may be that the efficiency is too low. It may be that the adequacy is too bad and there are many problems.

Oooo patient programs often have the following symptoms:

1. Too many differences: the rate of reuse of each type is low, resulting in too much memory waste. In general, such changes must be converted by means of commitment, or similar functional data must be converted into a unique type.
2. Too many commitments: although the commitment can improve the reuse rate, it will also make the object experience much larger, and the transaction efficiency will also be poor. It is always highly risky to assume that the website has been used. Even worse, it is probably a kind of negative correlation, making program programming worse. In many cases, it may be possible to use associate to change the role.
3. Too many objects: the aforementioned "too many differences" may lead to too many objects, but even if there are not many other objects, there is a chance to cause too many objects. When a program uses too many objects, it may cause a hard time for the program to write. In fact, objects can be shared with each other for many times.
4. Too many short-lived objects: this will cause too much construct and reclaim time, which may affect system efficiency. Many programmers have many short-lived objects, but they are completely unaware of them. You can use the object pool or other methods to change the volume.
5. Too many sensory components: "Too many objects" is already bad. If these objects are sensory components, it is even worse. The compute component consumes a lot of CPU computing power.
6. Too many parallel rows: in fact, from the perspective of OO first, every object is the most object-oriented, but this is actually not feasible, because the hacker uses too many OS resources, the efficiency may be poor.

If you want to renew Oooo, you need to spend a few years. It is recommended that you study Java swing well. This is an API that sends oo messages to the production environment without losing the flexibility and efficiency. None of the above six oooo symptoms are available in swing, and swing design is clever.
Oooo is not good, but do not use oo because of food consumption. Even Oo is good, but even good things need to be measured. If you want to introduce the program Oooo, you may wish to learn some good design pattern and understand the operating system, compiler, and program Internal principles.

Author: Cai xuanyuan
Date: 02/25/2002