I have some personal opinions on the issue of introducing third-party components:
First, why should I introduce a third party component?
Introducing third party components, no more than two reasons:
First, the company does not have this development capabilities, and the company's existing technical capabilities cannot be solved.
At this point, you must introduce a third party component to solve it. However, there are two other solutions in this regard: First, the outsourcing will be completed by the master, and the other is to avoid the avoidance of the needs and user consultation.
Second, reduce costs!
By introducing third-party components, it can greatly reduce development cost, improve development efficiency, shorten the project cycle, which is inevitable, otherwise, it is better to develop, and no one introduces her.
Although this can solve the current problem of this project, it will inevitably bring a negative effect, and the following is divided into two ways:
The first way is divided into two cases:
External master or outsourcing to master development although solving the current problem, it is impossible to solve the problem of project subsequent upgrade development issues, and if you need to make secondary development, you also need to outsource to continue, this is The company is a constraint. If the two parties have a good cooperation, things must be very good. If one wants to get a bigger interest, the other party is pressed, and the result is very obvious, inevitably caused both parties. Unhappy, or bring other inconvenient things (current domestic mobile phone industries face similar issues).
This problem is only delayed by modifying this technical problem, and this problem is only delayed, not completely solved. The second-end period of the user is still possible in the middle and late periods of the project, or the same problem requirement is resolved on the second version. At this time, it will still face the above situation.
The use of the second way will also be divided into two cases:
The first is a third-party component with reliable upgrades and services. If the provider of this component belongs to a civil organization or individual, its condition will be similar to the first way.
The second is that the free third-party components are used, this time, the problem facing the project group will be similar in the development of the first case in the development of the upgrade or new version, but At this time, the problem proposed by the user tends to be higher than the previous phase, that is, it is necessary to make secondary development on this free third-party component. At this point, you need to study the source code of this third party component to rewrite or supplement the service content. However, if the original developers of this component cannot be contacted or others are reluctant to provide source code for reference, then this feature will not be able to reach the initial state of this problem. Re-arranged staff must also affect the progress arrangement of the entire project, because you also need to re-implement the first functionality. It is not both the other party to provide source code, and the readability of the code is relatively poor, or it is not readable at all, and it also faces a dilemma of rewriting.
Therefore, I personally think that the way to introduce third-party controls in the project needs to consider clearing the location of the product and the negative effects of this code, cannot be blindly introduced. However, if your product is only planned to develop this period, you will take a walk directly, not to prepare for subsequent research and development, then I suggest you can use a large number of third-party controls to achieve as many functions as possible, because this is the most Cheap and fastest implementation.
I have said so much, you are welcome to review the critical guidance. The kid listened to the teachings.
