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.

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.

Popular posts from this blog

On Pruning Your Passions

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…

The Insidiousness of The Slow Solution

In software development, slow solutions can be worse than no progress at all. I'll even say its usually worse and if you find yourself making slow progress on a problem, consider stopping while you're a head.

Its easy to see why fast progress is better: either you solve the problem or you prove a proposed solution wrong and find a better one. Even a total standstill in pushing forward on a task or a bug or a request can force you to seek out new information or a second opinion.

Slow solutions, on the other hand, is kind of sneaky. Its insidious. Slow solution is related the Sunk Cost Fallacy, but maybe worse. Slow solutions have you constantly dripping more of your time, energy, and hope into a path that's still unproven, constantly digging a hole. Slow solutions are deceptive, because they still do offer real progress. It is hard to justify abandoning it or trying another route, because it is "working", technically.

We tend to romanticize the late night hacking…

Why I Switched From Git to Microsoft OneDrive

I made the unexpected move with a string of recent projects to drop Git to sync between my different computers in favor of OneDrive, the file sync offering from Microsoft. Its like Dropbox, but "enterprise."

Feeling a little ashamed at what I previously would have scoffed at should I hear of it from another developer, I felt a little write up of the why and the experience could be a good idea. Now, I should emphasize that I'm not dropping Git for all my projects, just specific kinds of projects. I've been making this change in habit for projects that are just for me, not shared with anyone else. It has been especially helpful in projects I work on sporadically. More on why a little later.

So, what drove me away from Git, exactly?

On the smallest projects, like game jam hacks, I just wanted to code. I didn't want to think about revisions and commit messages. I didn't need branching or merges. I didn't even need to rollback to another version, ever. I just …