This has been a busy week; so much so that the previous post, HTML 5, Google Wave, and the Future of the Web was started last weekend, with some editing and additions each day, and them actually posted yesterday. Note that it says “posted”. I realized last night that I hadn’t actually finished it. So, if you read it and wondered what the heck did HTML 5 have to do with the rest of the post, here is my wrap up:
You may be wondering why I started this post discussing HTML 5. The newest version of HTML has been in development for years, and has had its share of controversy. Many developers and users have spent years pushing for effective use of web standards, with an eye towards XHTML use and support, which emphasizes the separation of content and style.
HTML 5, according to some, muddies the content/style waters too much, and will make it harder to preserve the gains that continue to be made.
However, with the timely announcement of Google Wave, it seems clear that HTML 5 is a game changer with serious potential, and that it will make many things easily possible that currently require a great deal of work and computing power.
For the next few years, at least, we will be working with web pages that, at best, will be coded to two fairly different standards. XHTML and HTML 5 will co-exist, and if web developers approach their task with an understanding of each, we can design sites around the standard that suits them best.
Perhaps the next iteration of HTML will be a unification of the standards, allowing everything to exist within one framework. I don’t know if that is possible (and don’t know HTML 5 enough to have a grasp of the differences between them), but I for one will be very happy to have two powerful and well-created standards to work with, and look forward to seeing what lies in the future.
