Revisión del libro "The Truth About HTML5"

Revisión y debate sobre el libro The Truth About HTML5 publicado recientemente. Tuvo lugar en el grupo Meetup HTML5 Spain.

Transcript

1. REVISIÓN DEL LIBRO "THE TRUTH ABOUT HTML5" @felixzapata @madridwordpress
2. SOBRE MÍ Desarrollador Senior Front End y Consultor de Accesibilidad Web. en Adesis. Coorganizador del grupo meetup Madrid Accesibilidad TICs. Organizador del grupo meetup WordPress Madrid. Piloto frustrado... aunque ayudan los simuladores. Aerotranstornado.
3. ¿POR QUÉ ESTE MEETUP? Hay docenas de libros sobre HTML5 pero en ninguno de ellos te vas a encontrar algo de este tipo: HTML5 introduces a handful of new elements to help us define the structure of a given web page, such as <section>, <article>, <nav>, <aside>, <header> and <footer>. We shouldn’t use them. They were made up on a whim by (probably) one guy in 2004 – and even he seems to have forgotten what their purpose is.
5. LA HISTORIA DETRÁS DE HTML5
6. HOW ARCHITECTURE ASTRONAUTS AND THE W3C TRIED TO KILL HTML XHTML 2 was a beautiful specification of philosophical purity that had absolutely no resemblance to the real world.
7. THE WHATWG IS BORN It´s ironic, isn´t it? The establishment (the W3C) was the utopian revolutionary, and the rebel outsiders (the WHATWG) were fighting for incremental conservatism.
8. IS HTML5 HYPE, SUBSTANCE, OR BOTH? In many ways HTML5 is, to put it bluntly, a mess. But it´s the most ordered mess we´ve had in long time.
9. HIXIE OR BUST HTML is now essentially in the hands of one man.
10. SHOULD WE JUST KILL OF THE W3C ALTOGETHER, OR EMBRANCE IT? We should dissolve the W3C and run the web like an open source project. No more specs, just commits. Does Linux need a standards body?
11. TL;DR The W3C tried to kill HTML and took us on a decade-long journey fo nowhere; some people from browser vendors formed a group interested in web apps and evolving HTML´s forms; the worked outside the W3C on what became HTML5; the W3C realized they were screwed and agreed to use their work;
12. THE TRUTH ABOUT HTML5´S STRUCTURAL ELEMENTS
13. <HEADER> So this element doesn´t do anything now, and probably won´t do anything in the future. It´s the semantic equivalent of a tree falling in a forest with no one around to hear it.
14. <NAV> DISCREPO Good Intentions; Accessibility Disaster
15. <SECTION> Sections == Outline
16. <ARTICLE> Yep, another semantic term with an unintuitive meaning. If a element has such broad meaning, how can it be more semantic?
17. SO, WHAT´S THE DIFFERENCE BETWEEN <ARTICLE> AND <SECTION>? The very fact there´s a debate at all demonstrates a failure in the spec. If you have to debate an element when implementing it, you lose. A note to those teaching web standars: if you really hate your students, ask them to explain the difference between article y section
18. <ASIDE> Why should a pull quote be its own section?
19. <FOOTER> Like <header>, <footer> doesn´t actually do anything.
20. WHERE IS MY <CONTENT> ELEMENT? There really is no <content> or <main> tag.
21. CONCLUSION: R.I.P. HTML5 STRUCTURAL ELEMENTS If people do just use these elements instead of classes (wich they already are), they won´t be considering the outline they´ll be creating.
22. THE TRUTH ABOUT HTML5 AND SEO HTML5 does not help SEO. HTML5 for SEO is about as effective as homeopathy.
23. THE TRUTH ABOUT HTML5 MICRO-SEMANTICS AND SCHEMA.ORG
24. LET´S TALK ABOUT SEMANTICS In my view, the new elements are 'more semantic' in the same way a fruit-flavored candy bars are 'more nutritious' --not at all.
25. THERE´S NO SUCH THING AS "MORE" SEMANTIC But please, no more unqualified claims of 'But it´s more semantic' when discussing HTML5.
26. THE TRUTH ABOUT HTML5´S OTHER NEWS ELEMENTS
27. BE BOLD OR DIE TRYING If the HTML5 spec documented actual behaviour (i.e., 'paving cowpaths'), the spec would just say <b> and <strong> make text bold; <i> and <em> make text italic, and screen readers tend to ignore them altogether. That´s the reality. Everything else is fiction.
28. SHOULD WE EVEN USE THESE OBSCURE LITTLE TAGS? The address element has been around since the HTML3 spec was drafted in 1995, and it continues to survive in the latest drafts of HTML5. Bu nearly fitteen years after its creation, it´s still causing confusion among developers. So how should we be using address in our documents. Perhaps, after 15 years, it´s time for a rethink. What´s our aim here? Are we going to give it another 15 years? After 30 years, will the web finally be using <address> correectly? And if it is, so what?
29. THE TRUTH ABOUT HTML5 FORMS
30. PUT THIS IN YOUR FORM AND SMOKE IT XForms, recomendación del W3C en Octubre de 2004. (¿Quién estuvo en Fundamentos Web 2005?) It was powerful, but completely useless for the web.
31. 2005, EL COMIENZO DE LAS LIBRERÍAS DE JAVASCRIPT Prototype, jQuery y muchas otras desarrolladas han proporcionado, mucho antes, las funcionalidades que el WHATWG ha querido realizar mediante HTML
32. INPUT TYPE: COLOR (COLOR PICKER) For some reason, HTML5 also specifies a color picker.
33. THE TRUTH ABOUT AUDIO & VIDEO IN HTML5 HTML5 <video> and <audio> have become almost mandatory for media delivery for one reason: iOS.
34. PERO AL FINAL, NO SÓLO POR IOS En 2011 Adobe anuncia que abandona el plugin de Flash para móviles para centrarse en las aplicaciones nativas y en HTML5. Y encima: Developer guidance for websites with content for Adobe Flash Player in Windows 8
35. WRAPPING UP My advice? Keep an eye on what your favorite media player supports, and let it do the hard work.
36. THE TRUTH ABOUT HTML5´S CANVAS, GAMING AND FLASH
37. FLASH IS DYING, AND HTML5 IS ALL WE´VE GOT No iOS support from Apple, no future Android support from Adobe, and now no Metro support from Microsoft.
38. CAN CANVAS AND HTML5 FILL THE GAP? Veamos los escenarios: Anuncios Multimedia Juegos Sitios Web: "There´s a niche in converting Flash-based restaurant sites waiting there for someone!"
39. ¿MI OPINIÓN? Nunca o casi nunca nos leemos las especificaciones. El autor justifica muchas de sus opiniones por el uso del JavaScript. Usemos más los valores landmarks de ARIA.