"Cross-terminal web" reading notes

The cross-terminal web has become a trend, and this book is about the common problems of development under this trend and its solutions, which may be confined to space, and each aspect has not been elaborated, but this is so that the book is full of dry, almost no nonsense.

Here are some notes.

The intrinsic nature of the web is low cost cross-platform but not enough support for advanced features of the device.

The convergence of web and client applications has become inevitable! The basic skills of the front-end engineers also include knowledge of the client and server-side environments.

Mobile first.

Cross-terminal in addition to the response, also including multi-site, multi-template, multi-platform. There are many factors that need to be considered in terms of requirements and complexity, using the right approach.

Response-style bottlenecks:
The response does not solve the problem of mobile Dom redundancy, and JavaScript scripting redundancy is also a problem.
The nature of response depends on the difference of CSS processing level, but the difference between the mobile and the PC is not only the display, but also the differences in the form of the interaction between the DOM structure.

Disadvantages of multi-site:
Need to maintain a lot of pages;
Two level domain name too much, increase the cost of server jump.

GBS (Hierarchical browser support) idea:
Maximize test coverage with limited test resources.

"Cross-terminal web" reading notes