When doing technology, you should always consider optimization. This should be the consensus of every developer. Coding that is more concise and performs better has strong adaptability and higher scalability, and is also of great significance to improving one's coding ability. Regarding the impact of the level of hierarchical nesting of CSS on performance, the performance of the CSS2 series version may not be reflected much, but in CSS3, through the operation of various animated elements and selectors, the load of the browser engine is compared css2 has increased in magnitude. The browser's rendering of web pages is single-threaded, so even if the configuration is higher, unexpected performance crashes may occur.
And the structure of the document has a huge impact on script writing~ To exaggerate, nested queries for DOM are like walls after walls.
I don’t know what you think. Anyway, when I write CSS, I give priority to the effect and ease of maintenance, and I will talk about performance later. . .
I agree with the above view: When doing technology, you must always consider optimization. This is not only responsible for the project and the code, but also an attitude towards oneself.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
When doing technology, you should always consider optimization. This should be the consensus of every developer. Coding that is more concise and performs better has strong adaptability and higher scalability, and is also of great significance to improving one's coding ability.
Regarding the impact of the level of hierarchical nesting of CSS on performance, the performance of the CSS2 series version may not be reflected much, but in CSS3, through the operation of various animated elements and selectors, the load of the browser engine is compared css2 has increased in magnitude. The browser's rendering of web pages is single-threaded, so even if the configuration is higher, unexpected performance crashes may occur.
And the structure of the document has a huge impact on script writing~
To exaggerate, nested queries for DOM are like walls after walls.
If there is no obvious parsing delay or performance bottleneck, why go to all the trouble...
I decided it’s not necessary. Don’t over-optimize if there is no performance bottleneck.
I don’t know what you think. Anyway, when I write CSS, I give priority to the effect and ease of maintenance, and I will talk about performance later. . .
I agree with the above view: When doing technology, you must always consider optimization. This is not only responsible for the project and the code, but also an attitude towards oneself.