Where is the progressiveness of vue reflected?

In Vue, progressiveness is reflected in the fact that Vue has few opinions, is not strong, and does not do more than its responsibilities; Vue can select other components based on the core functions, and does not need to integrate them all. Each part is independent of each other and can be used independently.

The operating environment of this article: Windows 10 system, Vue version 2.9.6, DELL G3 computer.

Where is vue’s progressive style reflected?

The meaning of progressive style: the least assertion, no more things beyond the responsibilities; each framework will inevitably have its own characteristics, As a result, there will be certain requirements for users, and these requirements are called propositions. The propositions may be strong or weak, and their strength will affect the way they are used in business development.

Progressive can be understood as: get what you use;

Because Vue has few ideas and is not strong. You can choose any other components based on the core functionality, and they don't all have to be integrated. As you can see, the so-called "progressive" is actually the way Vue is used, and it also reflects the design concept of Vue. In short, you can have many choices, and it is not very mandatory that you must use that method. Vue It only provides us with the view layer. As for the underlying implementation, there are still many choices.

Compare other frameworks with vue, you may better understand:

Each framework will inevitably have its own characteristics, which will have certain requirements for users. These Requirements are claims, and claims may be strong or weak. Their strength will affect how they are used in business development.

For example, Angular, both versions of it are strongly advocated. If you use it, you must accept the following things:

- You must use its module mechanism

- You must use its dependency injection

- You must use its special form to define components (this is present in every view framework and is difficult to avoid)

So Angular has a relatively strong layout Otherwise, if your application is not starting from scratch, but constantly considering whether to integrate with other things, these propositions will cause some confusion.

For example, React also has a certain degree of advocacy. Its advocacy is mainly the concept of functional programming. For example, you need to know what side effects are, what is a pure function, and how to isolate side effects. It seems not as intrusive as Angular, mainly because it is soft intrusion.

Summary:

It may not be as good as React or Angular in some aspects, but it is gradual and has no strong claims. You can replace one or two components on top of the original large system. It can be implemented; you can also use it to develop the whole family bucket; you can also use its view to match the entire lower layer of your own design. It's just a lightweight view, it only does what it should do, and doesn't do anything it shouldn't do, that's all. I didn't do anything beyond my responsibilities, I just did what I should do.

【Related recommendation: "vue.js Tutorial"】

The above is the detailed content of Where is the progressiveness of vue reflected?. For more information, please follow other related articles on the PHP Chinese website!