How to understand the difference between vue single-page application and h5 single-page application?

as detailed in the title:

vuewebpack


understand the core functions of vue: dynamic data binding and component-based development. With both of them can handle more complex business logic, it is really convenient to interact

.

but there is still the following confusion:

1. If vue is used to do single-page applications, then I can do it with h5 as well as introducing some other js files. Why should I use vue-cli to build?

2. Know that the application of vue must be more than a single page application, can you write a website? Write app? If it is the latter two, does it have a good compatibility package for browsers and mobile phones?

Note: hope to learn more about friends in related fields and elaborate on your views.

Mar.15,2021
The main function of

framework is componentization, data-driven


(1) vue can be written into several areas, and the corresponding css,js and data are automatically loaded in each area, which makes code management clearer and lays a good foundation for componentization
(2) as for the second point, Vue-cli projects are not directly related to the encapsulation of browser and mobile compatibility, but the rise of vue framework will naturally lead to some tools to help developers better complete the compatibility encapsulation of browsers and mobile phones, without having to write a lot themselves.


you have to figure out the definition of this kind of problem first. Vue single-page app is fine. What do you mean by H5? The kind of single-page promotional material posted in moments?

try to answer your question:

  1. Vue is a MVVM framework, focusing on two-way binding of data, so it is suitable for developing re-interactive applications, such as clients, chat tools, and so on. Vue-cli is a scaffolding tool that makes it easy for you to build an application framework quickly, saving you the need to assemble the tool step by step.
  2. there are many types of websites, not all of them are suitable for Vue development, and some modules may be suitable. It doesn't encapsulate compatibility, and it doesn't need to be encapsulated. On the one hand, most modern browsers follow the specifications and are not compatible; on the other hand, the MVVM framework is only responsible for the mapping of data and views, not really responsible for rendering, so even if there are compatibility issues, it is not the work of Vue.

so the essence of the question is that you are specious about the concepts in the question. I suggest you get your mind straight first.


https://juejin.im/post/5a0ea4.

Menu