Designing an HTML tag . . . is actually fascinating
I’m getting up to speed on the upcoming tech wave by reading the finally published “HTML5 Up and Running”, by Mark Pilgrim. That sentence just feels sad (though necessary), but the first chapter of the book is really, really interesting. In a section titled “A Long Digression into how Standards Are Made”, Pilgrim walks us through a three week email thread that covers the origin and (pretty much) final resolution of the IMG tag.
The thread begins on February 25, 1993, with Marc Andreesen writing:
I’d like to propose a new, optional HTML tag:
Required argument is SRC=”url”.
This names a bitmap or pixmap file for the browser to attempt to pull over the network and interpret as an image, to be embedded in the text at the point of the tag’s occurrence.
An example is:
<IMG SRC=”file://foobar.com/foo/bar/blargh.xbm“>
(There is no closing tag; this is just a standalone tag.)
This tag can be embedded in an anchor like anything else; when that happens, it becomes an icon that’s sensitive to activation just like a regular text anchor.
Browsers should be afforded flexibility as to which image formats they support. Xbm and Xpm are good ones to support, for example. If a browser cannot interpret a given format, it can do whatever it wants instead (X Mosaic will pop up a default bitmap as a placeholder).
This is required functionality for X Mosaic; we have this working, and we’ll at least be using it internally. I’m certainly open to
suggestions as to how this should be handled within HTML; if you have a better idea than what I’m presenting now, please let me know. I know this is hazy wrt image format, but I don’t see an alternative than to just say “let the browser do what it can'’ and wait for the perfect solution to come along (MIME, someday, maybe).Let me know what you think………
Cheers,
Marc–
Marc Andreessen
Software Development Group
National Center for Supercomputing Applications
marca@ncsa.uiuc.edu
For the next three weeks, a number of programmer types, including Tim Berners-Lee, discuss a whole range of ideas for how this much-needed tag should be developed. It’s worth a read or two, since it highlights several open source, design, and software dynamics. Even in the note above you see a bunch of things:
There is very little preciousness — about ideas, implementations, territory, intellectual/engineering integrity — to be found. I’ve worked with engineers, and written code myself, for almost a dozen years, and was surprised to the point of shocked to see how matter of fact, and yet rigorous, a group of programmers could be, especially on a medium (email) that was at the time new and where etiquette was still evolving.
The book is worth a read and this chapter is really illuminating.
You can view the Andreesen post and click through the thread here.
Just finished reading Michael Chabon’s Manhood for Amateurs, a collection of essays about being a father, son, husband, former child, and writer. I read the book almost immediately and instantly, underlining lots of passages and phrases (wasn’t available in Kindle). Interestingly, it looks like guys on goodreads.com dug it less than women (might be more accurate to say several man trashed it while women gave it consistently high marks).
In a different essay, he makes a point that actually snapped my head out of the book. His biggest gripe about Pixar is the way they make Sid the villain in Toy Story. When Sid puts dresses on the cowboys and mixes parts and breaks the toys to see how they work, Chabon asks, isn’t he doing exactly what kids are supposed to do with toys? I had unquestioningly bought into the movie’s narrative, but after that comment, the good kid reminds me of a nerdy toy collector, keeping things MIB (mint in box), and suddenly I realize that leaving aside the ham-fisted presentation of Sid’s sadism, I actually relate much more to the dirt and grime and dark of Sid’s place than our hero kid’s room. 