Where is the line between layout and front-end?

Good day!
Interested in the opinion of practitioners about appropriate use of tools like react, vue, etc.
Where is the line between the choice in favor of a clean layout and front-end libs?
Practiced layout the example layout with the result. And then IMHO it is clear that the front-end libs - overhead.
But for example found on open spaces of maketick also for practice.
If you approach the issue from the shake skill is sbrocca on webpack, vanilla js, scss and drove. But on the other hand there are duplicate items, the same sliders from block to block could react-ovsky HOC to put the logic of the slider (this is the second layout). Anyway after working with reactor began to look and see the layout as a set of components that can be reused, both in terms of logic and in terms of UI.
To think about the project components convenient and easy.
And, in principle, create-react-app or equivalent from vue it would be easier to work with than Assembly because webpack components, imports, lazy loading is a simple and intuitive syntax, DRY, support from editors/IDE scope for styles.(of course part of this stuff you can add in the webpack build, donning a such as pug for "component" of the imports, but I personally don't like its syntax).
But whether the power of such tools in this case, because the Assembly will be added, the source code for these lib, which will increase the app size and add 100% dependent operation of the site from js?
Where is the line when you can/need to do natively that would be less dependent on the libraries/framework/js and when to use a front-end libs?
March 19th 20 at 09:11
1 answer
March 19th 20 at 09:13
Solution
Where is the line when you can/need to do natively that would be less dependent on the libraries/framework/js and when to use a front-end libs?

When imposition layouts move on to the real task, like implementation of any of the service(social network, personal account Bank, booking service, delivery service with a private office, video conferencing etc), then you will understand.

For the layout of lindoso pull frontend frameworks does not make sense.
The second layout can be implemented in the React/Vue as a beautiful one-page app with client side routing. There is the booking of hotel and shop. Think not about typesetting, but about how such things as the booking and the store to implement will. Then maybe will understand why in frontend development using frameworks and where is the border.

But on the other hand there are duplicate items, the same sliders from block to block could react-ovsky HOC to put the logic of the slider (this is the second layout).

HOC is not used for this.

And, in principle, create-react-app or equivalent from vue it would be easier to work with than with the Assembly for webpack

While typeset layouts and not working in real projects it may be more convenient. And Yes, create-react-app etc from Vue under the hood, use webpack.

Find more questions by tags FrontendIT terminology