HTML5 4 N00Bs
Starting With HTML5 in 2012
We all know it's making itself at home on our desktops and in our lives already. The new HTML5 is here to stay, and 2012 is heralded as being the year that 2013 will be the year of HTML5, but as coders we all know it is here to stay now and we're all starting to deal with it. You can't wait lest you be left behind the times at the roadside of ancient tech gazing at the gleaming new vehicles blaze by you. But rather than doing so alone, we have the advantage of the internet and collaborating with other like minds.
It is interesting to state that the newer HTML5 and CSS3 standardization incorporates visual effects that enhance the overall appearance of a website design without having to resort to extreme creative coding techniques. As detailed in my research results, How Computer-Generated Images Effect Human Visual Perception, the use of subtle suggestion in graphics and imagery can greatly improve how something is perceived. HTML5 has incorporated much of this so you wont have to go to great lengths to get, for example, rounded corners.
But far beyond that is the threat HTML5 poses on the rest of the web world. Long-standing Flash based coding will eventually fall away as it recognizes the power that HTML5 brings to the internet and its ability to handle complex interactive web applications. Even Microsofts Silverlight has already tossed in the towel having seen the power that is HTML5. With that much influence already being acknowledged, you can bet that the diehard devoted fans of such older technologies will eventually resign themselves to the obvious and begin learning HTML5 in order to progress into the future or be held back with the past.
Thus far, my own dabblings with HTML5 has been somewhat minimalistic, but I have coded enough of it to know that, for now at least, we still need to cater to older browsers. Techniques for doing so include such methods as using Modernizr to evaluate browser versions with either CSS3 or Javascript coding. The great thing about Modernizr is that you can include as much acceptible HTML5 coding as possible instead of just bypassing all the new, cool stuff altogether.
Last Updated (Saturday, 07 January 2012 14:32)