And I quote…

“But none of this answers the original question: why do we have an element? Why not an element? Or an element? Why not a hyperlink with an include attribute, or some combination of rel values? Why an element? Quite simply, because Marc Andreessen shipped one, and shipping code wins.”

“Scripting is here to stay, but should be avoided where more convenient declarative markup can be used. Scripting should be device and presentation neutral unless scoped in a device-specific way (e.g. unless included in XBL).”

I’m not sure that scripting should be avoided where possible in favor for declarative markup. My reasoning is that in order to get a page to DO ANYTHING you have to whack the declarative markup on the head to get it to change. How do you do this? JavaScript.

I do, however, strongly agree with keeping the languages as neutral as possible. Ubiquitous support and good, fast debuggability is key for developing any app.

By |2011-06-04T19:14:00+00:00June 4th, 2011|Uncategorized|1 Comment

One Comment

  1. Adam June 5, 2011 at 1:32 pm - Reply

    If the standard bodies want to maintain the largely stupid and meaningless distinction between markup and code, then they need to provide sufficiently extensible markup to allow us to avoid code for meaningless tasks. HTML 5 data attributes don’t really cut it, and you already have toolkits such as Dojo “abusing” them to implement functionality that would actually allow for markup to be used as desired. Why they couldn’t copy XML namespaces is entirely beyond me.

Leave A Comment

+ 27 = 37

This site uses Akismet to reduce spam. Learn how your comment data is processed.