Discussion on CSS and Table layout in Web Development

　　Fire Station building school (bkjia.com) NewsRecently, the debate on CSS and Table la s emerged on the Internet. I initially did not agree: I thought the significance of CSS layout had been deeply rooted in the hearts of the people, but I did not expect that there were so many designers and developers who had objections.

Let's take a look at your discussion and think about the two possible reasons:

On the one hand, ie6. Statistics on the Internet once showed that Web developers had the lowest input/output ratio for ie6. I believe that most front-end engineers have been gritted by ie6. It is better to use tables for refreshing and convenient layout with CSS.
On the other hand, I found that front-end engineers are increasingly pragmatic and focused on efficiency. Many of the new features of CSS2 and CSS3 have not been widely popularized, and the advantages of CSS, which the Web standard evangelists relish, are often compromised when it comes to reality. Although I have always been committed to the Web standard promotion, I have to agree that table browser compatibility is the best; table layout is easier for designers to get started. In the domestic environment, table cutting is still the most common way to create portal website topics or e-commerce website promotion pages. Its rationality exists.
Therefore, while advocating CSS layout, we do not need to make the table itself worthless to prove its superiority. In daily development, you do not need to abandon the table. The table itself has semantics, so you should use <table> when displaying a data table. during the development process, the layout of table + css should be used to weigh the cost. In this regard, we appreciate the pragmatic practices of front-end engineers of google and facebook. You can pay attention to the common pop-up dialog box with translucent shadow on facebook, which is made using <table>, which is also very subtle.

This debate, combined with the development of Web standards in recent years, has led me to think about the differences between improvements and reforms in Web development.

XHTML 2 tries to evolve directly to XML, announcing a break with HTML. This once panic my traditional HTML developers. When I saw that the WHATWG organization proposed HTML5 (which was finally recognized by W3C), I felt much more cordial with its gentle improvements. As it turns out, HTML5 is becoming increasingly closer and closer to us. Douglas Crockford even thought HTML5 was too violent and proposed an improvement solution for HTML 4.2.

Now let's look at JavaScript again. ECMAScript 4 Changes JavaScript to the next level. Fortunately, the Technical Committee is back to reason in the final stage, the re-proposed backward compatible ESMAScript 3.1 is obviously recognized by more developers who are truly fighting at the front-line.

Improvement, rather than bloody reform, may be a more practical and reasonable way to promote technological development. The evolution of Web standards is like this, product or project upgrades, and even the construction of social systems.

Original article: http://ued.taobao.com/blog/2009/06/24/web_dev_improve/