55 reasons to use XHTML-CSS when creating websites

Translation of the article "55 Reasons to Design in XHTML-CSS" .
In a random order, here are my 55 reasons to create only tableless sites, using valid XHTML for markup, CSS for formatting, and Flash only as an appropriate insert. By bestablichnost I understand avoiding the formatting of content tables (or "soup" from the replacement div div-s) and focus on the most semantic markup. Some of the reasons listed above explain “why not use plain HTML”, some “why not do everything in Flash”, some refer to both the first and the second.
I know that this topic has been discussed many times, but I will speak anyway

1. You may be referred to demonstrative sites such as zengarden , stylegala , cssimport and cssbeauty .
2. You do not need to spend extra time and energy thinking about the style of your code (write in capital letters or lower case, use quotes or not).
3. You do not need to think about which tags to close and which ones can (should) be left open.
4. You help search engines organize more relevant output by using semantic markup.
5. You will save on your traffic, and visitors will load your pages faster by reducing their volume.
6. It will be easier for you to upgrade to the XHTML 2.0 standard, which will provide even more semantic tools.
7. As soon as you practice enough, page coding will become easier and faster for you than with any table soup.
8. Which in turn will give you more time to take care of users.
9. Thinking about semantics will help you make design, information, and architectural decisions.
10. You can quickly create "raw" sites to test their information architecture, and add a "beautiful cover" later and with minimal changes in the code.
11. You will be able to do the design after the completion of all the “internal” works, which will help your boss or client to realistically imagine how much time is left before the work is completed.
12. You will have the opportunity to explicitly link to your internal pages (unlike Flash-sites).
13. You can use browser features, such as reducing / increasing font size and back / forward buttons (as opposed to Flash sites).
14. Redesign and reconfiguration of the entire site will become easier.
15. It will be easier to perform the final touches at the completion of the design.
16. Simple markup makes creating a CMS much easier, or generally irrelevant.
17. Simple markup allows you to quickly connect to another developer.
18. You will be able to develop internal functionality completely independently of the external representation, even by two unrelated people.
19. You can play around with the details of your code, trying to please the search engines, without any harm to the appearance of the site.
20. You will have full control over the version of your print pages.
21. Your sites will automatically become available for all types of browsers ( eg voice browsers , translator notes ).
22. Popularization of web standards will make your work easier in the future, thanks to eliminating the need to write code for each browser separately.
23. When all items are closed, your code looks more elegant.
24. Correctly composed code ensures that your site is correctly displayed in more browsers.
25. Correctly composed code will allow browser developers to pay more attention to the development of useful innovations than to spend time supporting their “broken” code by browsers.
26. Your site will be supported by browsers in the future.
27. Your site will be better displayed on mobile devices.
28. You will learn the basics of XML, which has many other uses.
29. CSS files are saved in the browser's cache, which will allow you to reduce the response time and channel thickness required for your site.
30. Your documents will become easier to convert to other formats using XSLT.
31. Thinking about semantics will make you think more about your content.
32. Studying semantics will allow you to become more organized, which will affect the quality of all the documents you create, even emails.
33. You can add new technologies to your resume.
34. Modern browsers render valid documents faster.
35. You will feel better because you will know that you are creating websites “correctly.”
36. Web standards are supported by people like: Dan Cederholm , Jeffrey Zeldman , Jason Santa Maria , Shaun Inman , Cameron Moll , Douglas Bowman , Dave Shea ...
37. You will become a member of the “movement”, thanks to which you will make useful contacts.
38. You will become more respected by young browsers, which will increase competition in the market, thanks to which all browsers will become better.
39. Blink tag will disappear.
40. Hard coding standard will allow you to learn how to quickly identify their errors.
41. You can earn money by teaching others about it, for example, by writing a book.
42. You will have more opportunities when looking for work, thanks to new skills.
43. You better understand how browsers work.
44. You can use hacks and technologies with cool names like “be nice to Opera”.
45. You will begin to pay more attention to meta-information, document typing and encoding assignment.
46. With more people in the world making smaller pages, the flow of global traffic will decrease, which will improve the speed of the entire Internet.
47. XHTML sounds cooler than just HTML.
48. More people reflect on the advantages and disadvantages, as well as ways to use XHTML, which creates more space for sharing experiences.
49. You can use almost the same markup for different sites.
50. When you learn how to write code faster and easier, you can refuse expensive software.
51. Google says that ( compares the number of results for requests, approx. Translator ): 4,380,000 xhtml better than html> 4,370,000 html better than xhtml, 206 “xhtml is better than html”> 87 “html is better than xhtml”, 2,130,000 xhtml sucks < 10,300,000 html sucks.
52. When all browsers learn how to correctly determine the MIME type, you will not need to convert all your websites from HTML, it will be enough just to specify the correct type.
53. If more people start using XHTML, in the future IE will have to learn how to properly recognize the MIME type.
54. The level of accessibility of your sites will increase, in particular through the use of the alt attribute in the pictures.
55. There are simply no such number of reasons to make websites in plain HTML, or entirely in Flash.

Thanks to GogA for help with the translation!