Insights on Frontend Framework Evolution and Selection from Architect Zhong Qincheng

Introduction

Zhong Qincheng, also known as Si Tu Zhengmei, is a front‑end architect at Qunar.com and the creator of the open‑source Avalon framework. He has extensive experience with DOM, JavaScript, selectors, module loaders, and MVVM, and has authored the book "JavaScript Framework Design".

Current Role and Experience

He leads a team focused on React and React Native development, building mobile‑first solutions for the company. His journey into front‑end began by chance through a sibling, and he has written over a thousand blog posts on the subject.

History of Front‑End Frameworks

Early frameworks like Prototype, Dojo, Closure, and YUI were created by large companies, but jQuery’s simplicity caused many of them to fade. The rise of RequireJS and Node.js introduced module handling and server‑side capabilities, leading to MVC frameworks such as Backbone and later MVVM frameworks like Knockout, Angular, and React. The rapid evolution is driven by continuous demand to move tasks from back‑end to front‑end for better user experience. Domestic development mirrors global trends, with companies like Alibaba building their own tools and Chinese frameworks like Avalon gaining international users.

Origin and Architecture of Avalon

Avalon started as a plugin for the early Mass Framework and grew into its own project with a community. Avalon 2 introduced a virtual DOM to improve performance, adding a fourth layer between the view and the view‑model. It supports multiple compatibility strategies: VBScript for IE6‑8, Object.defineProperty for newer browsers, and Proxy for the latest environments, allowing seamless property observation. Despite supporting legacy browsers, Avalon can produce lightweight builds for modern browsers.

Choosing a Front‑End Framework

Framework selection should serve business needs, consider code maintainability, and match team capabilities. Over‑mixing frameworks (e.g., Angular, Vue, React) can cause chaos; a consistent, well‑understood stack is preferable. Start‑ups may favor rapid‑development frameworks like Vue, Avalon, or React, while teams with many newcomers might stick to jQuery and Bootstrap.

Standardization and Future Trends

Some DOM methods have become standardized (e.g., append, remove), but browser vendors rarely coordinate, so frameworks remain essential for cross‑browser consistency. Framework competition will continue, with new designs periodically displacing older ones.

Advice for Learning Framework Design

Foundational knowledge in algorithms, data structures, and design patterns is crucial. Reading source code of successful frameworks accelerates learning. Testing, packaging (npm, CDN), and community promotion are also key to a framework’s longevity.