Quote:
Originally Posted by webdev1958
[ot]
html5 is still in development and will be for quite a few years yet. So why use a currently half baked html5 standard which may be different when it is finalised years down the track to what it is now. 
[/ot] |
i guess my best answer comes in the form of an example.
when i wrote
this image editor, it was for a class project in which we had to make any webpage. It was a neat web page, but it only worked in firefox beta 3 (gran paradiso).
my instructor had made the mistake of saying that photo-editing cannot be done in javascript...
there was no chrome at the time (2007), and no other browser really supported the html5 <canvas> tag in full. In short, i was coding to a promise; less than a draft, a single-browser maker's idea of a spec with their own fill-ins to boot.
years later, i discovered that it functioned on an i pad. it worked in chrome. IE got banned for life back then, but i could probably make it work in IE9/10 with minimal fuss. About a year or so ago, I did spend about 20 mins making a default layout for touch-screens that can't use drag and drop. That's the only touches to the code i'd made in years...
the lesson is much the same as from the early 20th century when cars were getting better, faster, and cheaper every year. Many folks said they were waiting for the price and performance to get to a certain level. When it did, they wanted to wait until it got even cheaper. Henry Ford pointed out that cars will always get cheaper and faster, it's a matter of how long you want to walk before you start driving.