Skip to main content

How To Walk Backwards to HTML 5

The more peeks I get at the HTML 5 spec, the more I dread it. We have barely shaken the last strongholds of crap-HTML since gaining some sanity some years ago. We put content in pages and we control style and layout in CSS, supposedly. Now, we see upcoming tags like article and nav and section, and all of it harks back to the days that were so dark in the web. I don't understand it.

If anything, we should take the suggestions of Douglas Crockford to heart. I want semantics in my content, not layout or anything related to it. I want themes and templates understood by the standard, not developed by a thousand projects in parallel resource squandering.

Any complaints I make about the upcoming HTML spec is completely trivialized by the fact that there is an upcoming HTML spec. Do you know how long it has been since any major shift in web formats? We're talking pre-Mozilla days here. I can't imagine the migration required with an internet the size we have today. The web makes a great platform, in my eyes, but upgrading the platform itself is working with the world's most ineffectively administrable network. Deploying can take years, even nearly to a decade.

We need to hold ourselves steady on the standards we can't even agree on today and just stop jumping on them. Break the foundations, crumble them down. Browsers are great at just working with what they're given. There is no such thing as an error, only being less affirmative. If we can take advantage of that, through arbitrary tags and attributes, we can really build something out of less.
Labels:

Comments

Ycros said…
But tags like article, nav and section do have clear meanings - parts of our pages already have these sorts of elements, however currently they are represented by div soup. I don't think anything has changed in terms of layout, you will still have to do all of that with CSS.

I suggest you take a read of the actual HTML5 draft specification, it clearly outlines what each tag is about.
6:35 AM
Post a Comment

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...
1 comment
Read more

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful...
1 comment
Read more

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro...
4 comments
Read more