About two years ago, DIV CSS was a very attractive combination. People who could use DIV CSS to create web pages were often given thumbs up. I remember that in early 2006. , I used div css layout for a pure static website and won an award in the school web design competition.
Today, although many people will be enthusiastic when it comes to DIV CSS, I will shake my head: DIV CSS is not everything, let alone what some people call a "myth"! It is CSS that creates the myth, not DIV CSS. I think it's time to correct this problem.
The essence of CSS is that each tag should be used for its own purpose.
Blindly advocating DIV CSS will only lead novices astray.
1. DIV is just one of the most commonly used tags in HTML
Obviously HTML is not just a useful DIV tag. Each tag has its purpose, but DIV is the most useful one. That’s all. If DIV could achieve the functions of all other tags, then the W3C would have streamlined HTML long ago!
Table is not without merit. It is just that using table is relatively simple and easy to use, so it was mistakenly widely promoted in the early days. However, the performance of table in processing web page data cannot be replaced by other tags. However, it is not suitable for the layout of the entire page.
2. Code readability
The code readability of pure DIV CSS websites is undoubtedly very poor. Even tables can use tr and td to distinguish rows and columns. A bunch of DIVs are stacked together. If there are no comments, you have no idea what a certain part is used for.
3. Semanticization and structuring
Nowadays, when developing CSS, more and more attention is paid to semantics. In the final analysis, semantics is still a matter of code readability. . Semanticization is to make the code more readable and understandable. For example, .text_01{color:red} is not as easy to understand as .text_red{color:red}.
The same is true for HTML. For example, when we see
tag, we know it is a paragraph with text; when we see You will know that this is a text unit smaller than ; when you see ,
, you will know that they are titles.
Obviously, this is not visible on a page that is all divs.
The same is true for the structure of the page, such as
I believe that developers will have a deeper understanding of the semantics and structure of code.
4. Teamwork
Low readability, poor structure and semantics will make it more difficult for other members of the team to learn and maintain, which is very difficult for a team. A waste of time and energy.
In fact, the term DIV CSS has taken us from table to another extreme. Correct web design is not about one tag dominating the world, but about using appropriate tags for each element.
So, DIV CSS needs to be said in another way, isn’t (X)HTML CSS more appropriate?
Please don’t specifically mention DIV again. Novices will really treat it as a treasure!
In fact, looking back at the process of popularization and standardization in China, we have already gone down the wrong path. When foreign colleagues are studying technologies such as CSS Sprites and Grid, what are we doing? When foreign CSS frameworks are blooming everywhere, what are we doing? Until now, we can only go to foreign countries and still follow others.
Two years later, we are still struggling with DIV CSS...
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
