Shulou(Shulou.com)06/02 Report--

This article mainly explains "what are the advantages and disadvantages of the Web framework". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what are the advantages and disadvantages of the Web framework?"

Do I need to use a framework?

It would be a dereliction of duty not to try to answer this question, which is increasingly becoming a mantra for some people in society, and the debate on the web platform has grown to the point where it is easier to create Web applications without writing extra API. Like all the content in this series, most of our answers are based on them.

Although it can work without a framework, it comes at a cost. Those who advocate frameless handwritten Javascript, who are often thought of as Stockholm syndrome (emotionally dependent and easily moved), forget that there are many sets of fast-growing API on the online platform, at least three different technologies, and three distinct grammars. The web platform has standardized and identified more than 12000 API, and in fact the Venn diagram in the browser shows these huge gaps.

If you are a person with deep skills and experience, you can be honest not to use the framework. But what about the rest of your team? What about the people under you? Or when your decision gets you into trouble? In this case, we will see a team taking risks without a framework, and eventually they will find themselves creating a framework that needs to be maintained on their own. Then there will be the problem of finding talent, they do not need to know how the framework works, they just need to look for highly skilled people who will call the network platform API or some people who claim to be experienced, only to find that they lack the depth and experience of skills that are conducive to team development.

Teams should avoid the trap of false equivalence (false equivalence). It is clear that companies that are innovative in the application of web technology are constantly improving their market value and competitiveness. Google, Facebook and Netflix are good examples. But this is not the case for most companies, and they should admit it.

Angular 2 +

What are the advantages?

The biggest advantage of Angular 2 + is its popularity. Others think that its name, which is closely related to Google, will affect the team's use of it. The rapid popularity of Angular 1 is because those from other interactive application development environments will find a similar model-view pattern for developing single-page web applications. By modernizing Angular 1 and rebuilding parts of the framework, Angular 2 + has really exploded, the number of formal and informal training institutions is impressive, and developers are highly competitive in the market. For users, it has a rich set of components for building user interfaces, which are one of the few frameworks in this series that can do this.

What are the weaknesses and challenges?

We feel that the Angular framework's emphasis on creating a user interface in a single page application does not address the larger concern of building a complete web application, which, if not determined early, will make the entire project difficult to maintain. in actual projects, it is often incredible to provide technologies that are not part of the core framework at runtime, which greatly reduces the value of TypeScript to the final developer.

Where will the future go?

Angular 5 has just been released, which seems to be that Angular has successfully confirmed the promise of a rapid release, and with the continued support of Google, Angular will become more and more mature.

Like many large organizations, Google has multiple (split) personalities, and from the outside, there is harmony between the Angular team and those who focus on browser standards. But our view is that harmony is just a thin layer of window paper. The Angular team doesn't have a real solution for web components and progressive web applications. We believe that the standards generally accepted by the industry will be gradually implemented in the Angular framework, which will affect how to better build Angular applications will become a medium / long-term risk.

When to choose Angular 2 +

If you need access to technical resources in a large framework, the technology within the framework is usually easy to migrate, or you need to train developers in the framework and have some confidence that they will acquire certain development capabilities in a short period of time, so you can consider Angular 2 +. It should be noted that Angular1 (angular.js) is completely different from Angular2+, and the applications, technologies and experiences in it cannot be directly transplanted to the development of Angular2+.

If your web application translates well into the standard model-view mode, you can also ignore others and directly consider using Angular2+.

If you are satisfied with the Google Material UX design pattern, then Material Angular is a quick, simple, and reliable way to follow the pattern.

React + Redux

What are the advantages?

The biggest advantage of React and Redux is their relative simplicity and focus. It is very difficult to do one thing and do it well, but both libraries achieve their goals very effectively. Although some state container methods may be external, most developers can easily grasp the concept, understand the benefits of an one-way data architecture, and simplify a large number of user interface applications.

What are the weaknesses and challenges?

The biggest weakness of React and Redux is not what they are, but what they are not. To build a feature-rich Web application, you need a lot of functionality, and once you leave the core of React and Redux and other libraries, you will find a very fragmented community with countless solutions and patterns that are not easy to integrate.

So while React and Redux are very focused libraries, inexperienced teams can easily build unmaintainable solutions without realizing that the choices they make can lead to poor performance or errors. Even experienced developers may realize that a loose architecture or convention may haunt them in the future.

Saving money is a kind of deception to yourself, and the adoption of React and Redux within the organization will easily reduce inefficiency. Without the extensive conventions and standardization of other libraries and patterns, standardizing React + Redux is more efficient than the JavaScript we are using to write our applications.

Where will the future go?

Facebook and React recently pulled away from cumbersome additional patent disputes, recognizing that, like other projects, the wider community can raise its voice. I think this helps Facebook realize that they don't know us better and trust us to lead the project. It is hoped that this will continue to run through the characteristics and technical direction of the project.

It is difficult to predict the future of React and Redux. However pooling libraries does improve adaptability significantly and most React + Redux patterns promote a separate architecture so that refactoring and iteration can be done easily. Two years ago, people liked React + Flux, but the whole community quickly embraced Redux. Other major changes in thinking or patterns can be easily adopted. This critical capability is likely to continue into the future.

When to choose React + Redux?

If you rarely need hands-on guidance and are looking for a better library rather than a comprehensive framework, then React + Redux may be right. In this process, you need to be honest not only with the capabilities of your team and organization, but also during your initial development process and throughout the long-term maintenance of the application.

Vue.js

What are the advantages?

Incremental build capability is the biggest advantage of vue.js, and vue has a concise and reasonable architecture that makes it easy to understand and build.

Vue has a strong community of passionate people, which adds great value to vue.js and makes it easy to create a comprehensive solution for a blank project.

What are the weaknesses and challenges?

The conversion between a model-view application and a state container type application can be confusing, even if it does not perfectly include a perfect transformation from one pattern to another, but it makes people feel like they want to maintain the correlation between the two patterns. This is at least confusing for those who expect the perfect solution for vue.js and may make it difficult to maintain inconsistent applications.

A bigger challenge is that vue.js relies on a single person. Obviously, other projects are basically supported by one organization, but it feels more meaningful. Although it has a strong documentation community and many innovative new projects, the development of the core of vue basically falls on one person.

We are pleased to see that vue is more receptive to emerging standard methods, but its pattern is similar to that of web components rather than real web components, which may outweigh the gain of vue.

Where will the future go?

Although vue.js has a wide range of applications, it is difficult to predict how long this momentum will last in the medium term. It is not directly supported and maintained by a business organization, so it largely depends on the viability of the maintainer and the desire to continue to maintain.

It also shows a certain degree of language adaptability, and continues to maintain its own language modernization and the times with the outdated and out of favor of some models. At present, there is no sign that the vue.js architecture can not adapt to further development in the future.

When do I choose Vue.js?

If you have a traditional web application and need a strong and robust application layer, then vue.js may be a good choice with a clear pattern that even inexperienced teams can use correctly or incorrectly. Although the vue UX framework does not have out-of-the-box functionality, a large number of applications can be continuously built on vue.js, which will benefit your project.

Dojo 2

What are the advantages?

Dojo2 focuses on the experience model of bringing more dynamic components built on the state container architecture, filling in many gaps in frameworks such as react+redux.

Dojo2 also knows that it is not only developing in its own ecosystem, but also aware of the need to support different application instances by including web component import and export functions, but it still provides a structured and inherent framework value, and the core foundation of Dojo2 is still focused on providing interactivity.

Dojo2 feels that it provides a large number of important functions and solutions, which is very important for building a complete web application, which is not the focus for most other frameworks. Providing an international system and a wide range of accessibility patterns is one of them, as well as a theme system and evolution model to ensure that it not only provides good code development for Typescript/JavaScript, but also manages resources like CSS.

Dojo2 focuses on providing a structured and ergonomic development environment. By using typescript and other development models, it tries to provide secure protection mechanisms to guide novice developers. By focusing on improving framework development efficiency and development security, it aims to enable development teams to quickly deliver better web applications.

What are the weaknesses and challenges?

It is debated whether the practice of further extending the release time of Dojo2 is hindering the development of the framework, while other projects can continue to develop and iterate rapidly due to the expansion of their resources, resulting in Dojo2 is clearly in a crowded competitive environment.

This may be a potential development opportunity and challenge, and it is hoped that Dojo2 can be used in terms of flexibility and interactivity rather than for other special reasons.

Where will the future go?

Dojo2 will be one of the excellent web frameworks in the future, and it will continue to strive to provide clear patterns and guidance for building extensible web applications. With the continuous emergence of new standards, Dojo2 will make further efforts to implement new standard methods in the framework, continue to try to expand the openness and interaction of the framework, and create solutions suitable for more people to use.

When do I choose Dojo2?

If you want to adopt a flexible, modern, responsive web application architecture, and you need a lot of intelligent default settings, then Dojo2 will be a good choice. You don't have to piece together and build a pipeline, and provide you with a higher-level command mode that allows you to focus more on the development project and confirm that it is prepared directly for you to produce and develop directly. In addition, if you understand the advantages of typescript, Dojo2 will strictly use typescript to manage and provide a robust developer development environment.

Ember

What are the advantages?

Ember.js is probably the most opinionated mainstream framework, which is its biggest advantage. It has the right way to create an Ember.js application, and there is usually only one way to create an application. Ember.js is more like a product or platform, where you will go to a supplier for long-term support and maintenance. Ember.js provides comprehensive version management for its platform, upgrade tools, and powerful guidance and tools for API upgrades. Maturity is a good summary of Ember.js.

Ember.js has shown over the years that it can maintain its framework and align it with modern standards without prematurely forgetting traditional browsers.

Ember.js has a clear and reasonable architecture for building Web applications across the board.

What are the weaknesses and challenges?

Ember.js is probably the most opinionated mainstream framework, which is its biggest weakness. Although the community is open and receptive to investment, there is still a need to find the right way out of the downward trend, which can be a challenging problem.

Having a rich third-party community can also be challenging. Since there are no out-of-the-box UX components, this is likely to allow you to use third-party suites. You may find that although these packages are not comprehensive, you will need to build or look for other components. Since Ember.js does not extend, you will find that you have inconsistent parts on how to interact and manage DOM, and do not provide an easy-to-manage interface.

Where to go in the future?

The main contributor to Ember.js is the core participant of the JavaScript language Standards Committee TC39. Over the past few years, Ember.js has had a more direct impact on the direction of JavaScript than any other framework. Our view is that this will continue to be affected in the future and help promote the features and patterns of JavaScript. This also means that Ember.js will continue to maintain a close relationship with future standards.

Ember.js is unlikely to disappear at any time in the future, although their innovation is likely to be achieved through other projects closely integrated with Ember.js, such as Glimmer, which provides a new UI framework for Ember.js applications, which is based on TypeScript.

Why did I choose Ember.js?

If you look for maturity in the framework, then Ember.js is hard to make mistakes. In addition, due to the understanding of the content provided by Ember.js, extensive official and officially recognized training, and strict structure, it may be easier to find people who can build Ember.js-based applications than other frameworks. You can also teach large teams how to build applications and ensure common dialogue and understanding for the entire team.

If you want to maintain confidence in the community and think critically about changes in their platform, then Ember.js can be a good consideration. You can spend less time following current technology trends and focus more on creating applications.

Aurelia

What's the advantage?

Aurelia has a lot of methods, structures, and ideas for building Web applications. The writing of this framework has many technical advantages.

What are the weaknesses and challenges?

We estimate that the biggest challenge is the lack of motivation for core development and critical materials. We feel that many ideas and concepts are our critical ideas about other frameworks, but these aspirations are not fully delivered. It seems like a work in progress, like Dojo 2, but it is already a released framework.

Most Aurelia sits on a person's shoulder, and if that person's attention or usability changes, it will be challenging.

What will happen in the future?

For Aurelia, there is a big opportunity. If it can achieve his vision, he will preserve the existing template for building Web applications in its entirety, but deliver it in a more robust and complete manner. We don't know if Aurelia can make full use of this opportunity.

Why did I choose Aurelia?

If you are committed to the Web model view application module and you and your team are trying to do something better, then Aurelia is an option. It is like a framework that is looking for a larger community to help it develop and evolve.

Thank you for your reading, the above is "what are the advantages and disadvantages of the Web framework" content, after the study of this article, I believe you have a deeper understanding of the advantages and disadvantages of the Web framework, the specific use of the need for practice to verify. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.