2012, css-tricks.com website:
versus:1992, standard OS / 2 interface element:')

I am convinced that CSS and HTML are a dead end in the development of the idea of markup languages and the time has come to abandon them altogether rather than improve them. Therefore, I urge all serious programmers not to code anything at all directly in them or even to use frameworks close to them in terms of semantics.
Create your markup languages and, if necessary, translate them into HTML + CSS. As a result, one of you will come up with a powerful and crystal clear replacement for this historical hack of layers.Modern web technology based on CSS / HTML (including even HTML5 / CSS3) is the apotheosis of unsystematic architecture and fragmentation. The lack of system in the initial design and the subsequent imposition of fragmentation on it due to incompatible implementations in browsers gave rise to hack cascades for patching holes. These hacks (like CSS 2.x) are already more systemic in themselves, but their developers are connected by the field (HTML / CSS 1.x) they have to play on. Therefore, new versions of CSS do not solve much, moreover, they are not fully supported in real browsers.
Opening any serious CSS file, for example, written in Google or FB, you will see negative element borders in it, relative positioning through pixel shifts, huge lengths, then truncated with overflow: none, using the content property and other perversions. These are semantically meaningless and unreadable constructions by other programmers. But without such things it is impossible to create a modern web-two-zero site. Or, for example, it is not written in any CSS specification that a picture from the <IMG> tag, following the <OL> with the image marker, can be inserted visually between the marker and the text of the list items (in some browsers and with some layout options) .
Laying out a serious website using CSS / HTML is a modern shamanism, the techniques of which are transmitted “from father to son” (from one web designer or programmer to another), not as scientific knowledge, but as a set of learned craft rules. Often, web programmers and web designers using someone else's technique do not even have a clear model in their head, why it works this way and not otherwise.
Indirectly confirms this assessment and the fact that almost all serious companies make native mobile phone applications, and do not offer their users to open their website in the browser. Although it would seem, to create another template for the site is an order of magnitude simpler task than to create and maintain a separate native application. And note that there are no IE 6, 7 and 8 on mobile phones :) and the problems they have generated. But they make applications, not websites.