What is front-end modularity? Do the components of vue count?
after reading many recruitment requirements, "modularization" is mentioned
I am now developing with vue
I encapsulate the paging into a component and introduce this component when I use it. Is this modularization?
I encapsulate the breadcrumbs into a component and introduce this component when I use it. Is this modularization?
I encapsulate the pop-up window into a component and introduce this component when I use it. Is this modular?
are these considered modularization?
if not, can you give a specific example of modularization
count.
but come here to ask such a question, which shows that you don't understand the true meaning of modularity-using front-end components to solve engineering problems can only be regarded as touching the threshold of modularization, which is still a long way from mastering its meaning.
Modularity is a very common concept in the software industry. You read it right, not just the front end, all the aspects related to the software, you have to mention modularity. In fact, most of the concept of front-end modularization comes from the back-end, which is why there are so many back-end nouns referenced in some front-end frameworks.
modularization solves the unsolvable problem that the software itself is bound to get bigger and bigger . Since it cannot be stopped from expanding, it can only be physically divided into smaller but more small units that can be internally autonomous and provide services to the outside world. Micro-service, componentization, modularization, the concept is more or less the same, but the core value demand is reasonable.
so, the core advantage of modularity is making things small . Reducing complexity, providing reusability, and improving the collaboration ability of the project team are all by-products, but they are the things that people are most interested in talking about.
the above is purely personal understanding, not to mention the truth, let alone the secret meaning. Because I have always believed that to understand the core of software development, you always need to put it into practice.
the hard word is modularization , not modularization . But when you say modularization, people can understand what it means.
Modularization is a general concept, which also applies to software development, allowing software to be developed separately by module, which usually uses a standardized interface for communication. In addition to differences in size, the separation of concerns between objects in object-oriented languages is basically consistent with the concept of modularization. In general, dividing the system into multiple modules helps minimize coupling and make code maintenance easier. Any class library is actually a module, whether it's Log4J, React, or Node. In general, both open source and non-open source applications rely on one or more external class libraries, and this dependency may be passed on to other class libraries. Any language has modularization ideas, such as java's package, es6's import/export, etc. Js happens to have experienced from scratch, and there are many js modularization specifications, AMD,CMD,UMD, and the official import/export of es6
the concept of componentization is mostly used in the front end. The meaning expressed by components and modules is similar. The components I'm talking about here are narrower components, referring specifically to the basic components of the page built in the front end. Component is the encapsulation of business logic, a page is composed of multiple components, and the component can be composed of other components.
for more, please refer to my Modularization and componentization
