|
" The i-Technology Blog "
Jeremy Geelan's weblog about i-Technology, i-Technologists, i-Technology Pundits, i-Technology Executives, and the ever-expanding i-Technology Lexicon | |||||||||||||||||||||||||||||||||||||||||||||||||||
|
Login Console
Mailing List
i-Technologists Adam Bosworth, Google Bob Mason, Brightcove Chris DiBona, Google Dave Sifry, Technorati David H. Hansson, Ruby on Rails James Duncan Davidson Jesse James Garrett, AJAX Joe Savard, neXplore John Patrick, Attitude LLC Liz Lawley, Lab for Social Compu Miko Matsumura, Infravio Nicholas Carr Tim O'Reilly Joshua Allen, Microsoft Grady Booch, IBM Jon Box, ProTech Tim Bray, Sun Derek Ferguson, Bear Stearns James Gosling, Sun Mitch Kapor, OSAF Eric Newcomer, IONA Alan Williamson, SpikeSource Jeremy Zawodny, Yahoo!
RSS Feed For This Blog Click to Receive RSS Feed
i-Technology Pundits Colin Crawford Dave Taylor Dion Hinchcliffe Paul Kedrosky Robert X. Cringely Simon Phipps John Dvorak Dan Gillmor Roger Strukhoff
i-Technology Execs Annrai O'Toole, Cape Clear Jeremy Allaire, Brightcove Jonathan Schwartz, Sun Michael Robertson, Linspire
SYS-CON Media & Events Real-World Flex Seminar SYS-CON.TV Interviews AJAXWorld Conference & Expo Upcoming SYS-CON Events
|
Crock Has Very Clear Ideas On How To Fix HTML
"HTML has long been at war with itself," writes Yahoo! Architect Douglas Crockford, one of the most popular speakers at AJAXWorld ever since it began life early in 2006. "Is it a document format or is it an application delivery format? You can see that confusion in the cacophonous HTML 5 effort." But Crockford has very clear ideas on how to fix HTML: his approach is to make it better by exploiting unrecognized properties that it has had all along. The background to Crockford's essay is as follows: the HTML 4 recommendation was published in 1999 and, according to Crock, while there are good ideas in HTML, "many of these were discarded in the XHTML effort." He continues: "My thinking is that we should take a step back and refocus. The problems with HTML will not be solved by making it bigger and more complicated. I think instead we should generalize what it does well, while excising features that are problematic. HTML can be made into a general application delivery format without disrupting its original role as a document format.The ten changes Crockford proposes can be read in full here. "These changes significantly improve the reliability, security, and performance of HTML applications," Crockford claims, adding that the simplification of the language reduces the cost of training of web developers and incorporates the best practices of AJAX development. "It provides extensibility without complexity. The deltas from HTML 4 are generalizations and reductions, which should make browser implementation more straightforward. This is particularly important for mobile devices that cannot tolerate the power demands of complex platforms. The only new feature here is the module, which is critical for security. Modules makes safe mashups possible."We can expect the discussion to continue vigorously into 2008, when Crockford will be keynoting at AJAXWorld Conference & Expo 2008 East, in New York City (18-20 March, 2008).
| ||||||||||||||||||||||||||||||||||||||||||||||||||