look how small your project is. The official documentation of Vue is already very detailed. The cost of learning is not very high. Developing a project does not require you to learn much about webpack.
the use of webpack, hot updates, code reviews, etc., obviously greatly improves the efficiency of development.
in addition: Vue ecology has been very prosperous at present.
there are basically corresponding versions of swiper and so on that you mentioned.
besides, jquery and its corresponding plug-ins can also be used in Vue. Although not recommended.
Vue also has many component libraries, including mobile, PC, such as element-ui, iview,ant-design-vue, etc., which have basic common components for implementation, such as the one you mentioned.
in short, the data-driven idea of Vue brings a lot of convenience.
where does vue-cli 3 get the learning cost?
A direct sentence
vue ui
build projects, install plug-ins, install dependencies, hot update development, and packaging under the graphical interface. Webpack is configured to be used right out of the box.
< H2 > about Jquery and Vue < / H2 >
ide/index.html-sharp%E8%B5%B7%E6%AD%A5" rel=" nofollow noreferrer "> Vue start
this article is learned using Vue as the code within the Script tag of a Html .
We can introduce multiple js in Html, so Vue.js and Jquery can also use CDN to introduce No problem
< H2 > about drawbacks < / H2 >
Vue is progressive, so we can use Vue as an auxiliary JS block
.
but one thing to note is
Vue ecology itself is to achieve single page & modular Web development
Local use of Vue will cause us to have multiple instances of Vue (it will be difficult to create a single page), and the code will be maintained in Script, and it will be difficult to modularize the project without using Webpack.
< H2 > so what can we get? < / H2 >
using Vue (CDN to introduce) We can:
- data driven
- MVVM
- certain componentization ability
- more convenient rendering page elements (such as which elements are rendered and hidden based on permissions)
.
it is important to note that these advantages are only valid within "Vue instances"
above is my personal understanding, there may be mistakes, but I hope it can help you
there is such a project, https://github.com/tower1229/.
.
when I first learned Vue, I had the same idea as you, so I developed a single-page application using vue.js manually without CLI tools, and realized single-file component development by using seajs in disguise.
disadvantages:
- because the development code is not packaged and built, the development code runs directly in the browser, so the loaded files are relatively fragmented, and the number of requests is relatively large, but it has little impact on small projects
- it is true that no hot updates are slightly slower than the way CLI tools develop servers
to tell you the truth, I also directly introduced vue to do the company's small projects before, just like jq, and the plug-in ecology is also good, basically all can be found, but it is really not as convenient as the whole family bucket, ah, the whole family bucket you just use, if you don't go deep into it, it is still easy to operate, so it is recommended to use the whole family bucket!
for front-end projects, do you think packaging tools or frameworks can be saved?
vue is a progressive front-end framework.
you may not understand what progressive is.
vue I don't think the cost of learning is high, not to mention that there is such a thing as vue ui , which is very fast to configure. In addition, do not use jQ to set up vue, since it is MVVM and engineering, you have to go to to learn something different, right? If you try to call it in the same way as jq, you may end up stepping on more holes than the regular way of playing.
in a word, the easier it is for you now, the harder it will be for you to go deep into it.
will it be bad for the later SEO if I introduce vue.js to develop a large mall project?
