Why should I use Vue.js in my projects rather than not?

Question

Fonts

Good afternoon [ I am writing vue.js - I mean vue.js, react.js, angular.js
]

1. Is Vue.js jquery tweaked or do they solve different problems?
   
2. If I learn Vue.js can I ditch jquery entirely?
   
3. What can Vue.js do for landing pages compared to jquery?
   
4. What can Vue.js give for a site up to 10 pages, compared to jquery
   
5. What type of projects clearly show the benefits of Vue.js
   
6. In what cases will you use Vue.js [do not write in all, write for example: store, cat block, etc.] ?
   
7. What tasks [typical and personal] would you solve with Vue.js ?
   

The purpose of the question is to decide for yourself whether to learn vue.js or not.
This is my first touch on js frameworks, so explain like a five year old

Answer 1

Very similar to FF Cocon , but there are differences.

Answer 2

1. these are different things
2. if it is not tied to components using jquery (although the same bootstrap is untied )
3. nothing, since landings usually have little logic, the difference is felt when the number of links increases
4. depending on what kind of pages, see above
5. single page applications, rich internet applications
6. when an input/block appears, the content of which is associated with some data that changes in another input/block
7. thousands of them. for example the table with the filter entirely on the client.

Answer 3

When too many tables appear in a project, we cannot be sure that we will fix them all in one fell swoop, it is difficult to write code that works with all tables at once.
And when, in case of an error in the logic of working with the entire database as a whole, you need to edit not only the API but also your frontend - layouts, outputs of elements, and so on - it becomes very sad and the desire to work disappears.
Using the front framework, of course, we strike at the SEO of our site, but then we can only do the API, and entrust the development of the external part, for example, to another person.
Of course, this will strain the server with a large number of requests per second in order to update and synchronize data, the approach to work will also change. But in the case of layout, more load goes to the Internet connection channel - transferring 100 kilobytes of layout back and forth constantly for each page anew.
With the front application, you gave them 1 time, and then work with the data, the front builds further layout from the pieces on the client side according to the data, without wasting memory and server processor. It works outwardly much faster, it seems that the site instantly exchanges data and everything is so fast.
But the main thing is not external, the main thing is that you do not need to be sad about changing the external part of the site when your work with the database is broken. You make an api and don't worry about rendering, which reduces the number of problems you have to keep in mind
. It's not "better", it's "different".

Answer 4

I think that first of all you need to know js well and then choose which of the frameworks and their concepts is closer and more understandable. At one time I raised my knowledge of jquery to a good level and now I know it, but this did not stop me from learning React. There are places where it is still more appropriate to use jquery, but these are very specific tasks. The main part of the tasks, let's say, 80 percent if not 90, I solve on react. I think the main advantage of all the frameworks that you listed compared to jquery is speed and the concept of components. Maybe somewhere part of the application will fall off, while the rest will work fine, which can not be said about jquery. The concept of Components also helps reduce code duplication and component reuse.
In general, there are many for and few against. In any case, it's up to you.

Answer 5

1) Vue.js is jquery upgraded or do they solve different tasks?
They solve different problems. jquery is a quick way to file a button click and submit with AJAX.
2) If I learn Vue.js, can I completely abandon jquery?
For yourself, yes, if you freelance, then no. Most jQuery sites
3) What can Vue.js do for landing pages compared to jquery?
Yes, actually nothing. 4) What can Vue.js
give for a site up to 10 pages, compared to jquery
A for 20? 6) When you need to quickly make an admin panel on the bootstrap, so that everything works through AJAX, so that there are components and so on.
7) Filter in the online store, order form, admin panel.

Answer 6

There are quite a lot of detailed answers above, so I’ll only note one of the advantages of Vue regarding sites - it’s good that you can write in an isomorphic style and have both template rendering on the server (SEO is important for sites) and rendering on the client to improve usability and interactive things.

Answer 7

First you need to ask yourself: what is the SPA framework for? The abbreviated answer will be short: to decompose large complex parts into simpler and more understandable soapy ones (which communicate with each other). In the case of a landing page, you hardly need a SPA framework, just add a boilerplate (that is, add complexity to the project, which contradicts the original goal of the framework), and you probably don’t need jquery either (except perhaps as a mandatory dependency for some then ready-made interactive solutions, sliders / galleries).
To study any SPA-framework or not? Well, ask yourself, what kind of tasks do you want to do, do you want to rivet landing pages? Or do you want to work in a team to create services like the one on which you just asked the question (because here the use of the SPA paradigm would be appropriate)?
In the context of what has been said, try to answer for yourself point by point.

Answer 8

Is Vue.js jquery tweaked or do they solve different problems?
Vue is a full-fledged framework based on the MVVM pattern, and jiquery is a library for calling the necessary prepared functions to stupidly manipulate the DOM.
Everything is possible if you understand how to do without jquery in print.
Interactivity, animations, flexibility in the interface, various web components that can be inserted anywhere and even swapped on the go.
Smaller page weight (no need to reload), less response to transitions between pages (vue-router), you can use it partially (that is, most of the content is loaded by the template engine), and in asynchronous sections with interactive - use the view framework.
In any where asynchronous is needed, and Ajax requests jikveri you are sick of it. That is, for the most part - working with data. If you need to dynamically build a comment tree based on data, then vue does that better.
It is already possible to write native applications, which is partly why mobile applications are needed, in projects where components are needed that are easier to make on Vue than to put on jiquery.
Animated block transitions, interactivity, asynchronous calls and plotting, infinity scroll page
To work for my uncle - learn angular / react, but I see the Vue community is more loyal and maybe work will also appear.
This is my first touch on js frameworks, so explain like a five year old

Answer 9

1) Both Vue and jquery are all high-end JavaScript, it's just that Vue is more high-quality and corresponds to the current time and modern approach to development
2) Most likely yes, moreover, using Vue to pull jQuery there is bad manners and bad practice. There are exceptions which are listed below.
3) This is the exception. The only place I've used jQuery so far would be the simplest landing page. Although who am I kidding in 2018, I would have been better off writing a regular landing page in pure/vanilla JS.
4) Components, data binding to view (not to be confused with Vue), convenient routing, the ability to use a single storage, and so on.
5) In all projects the size of which is larger than the landing page.
6) In all projects the size of which is larger than the landing page.
7) In all projects the size of which is larger than the landing page. Pet project - SPA, working project - big SPA.