It’s time to clarify a few things which have been bothering me in recent times. There seems to be a substantial backlash against the entire HTML5 standard, most of it from Adobe supporters. At the same time, I’m not a subscriber to the Apple as a whole against. Adobe debate, I believe it’s ridiculous. There always will be corporate politics. But to me, as an individual developer and end-user, I’m concerned about what the standards will do to be pushed further to allow for creativity and enhance user experience, bring together different technologies, and simplify my life. The entire “us vs. them” mentality is uninformed and naive. 

There’s no doubt that I’m ecstatic HTML5 Development but not because I believe Google and Apple have finally given Adobe the respect they deserve. Corporate spats are for companies to take care of and not you. They’re not your friends. They do not pay you to stand with them on the internet. It’s ridiculous. Recently, I’ve noticed many people putting forth arguments they can’t comprehend and are trying to damage the HTML5 project. In the end, these are the five broad categories in which the most common fallacious arguments can be classified.

It’s a phrase I repeatedly hear “HTML5 is a mess because companies can’t agree on the features”. It’s an outcome of unhappy Adobe supporters trying to make it appear like the debate over codecs can be representative of the entire standard…; of course, it’s not. Interestingly, the codec for video debate is confined to the video component https://inqsys.com/. 

Perhaps it is that they believe there is potential in the project? Is it necessary to make it an attempt to destroy Adobe to their nihilistic pleasure? Grow up. I’ve heard a variety of theories; I recently heard that because sure of the original members of WHATWG were Apple employees (among others from Mozilla and Opera), which means that Apple was effectively the owner of HTML5! No one owns HTML5 like Adobe is the owner of Flash, and no single company can dictate the standards, which is one of the most significant advantages of HTML5.

Google and Apple certainly can propel the acceptance of HTML5 forward, and this might indeed be at the cost of Flash and Flash, but that’s because Flash is old-fashioned and natural selection is not a hidden agenda. I’m not embarrassed to say that I’m an HTML5 user, but this doesn’t mean that I’m specifically supportive of Apple or Google or even in opposition to Adobe, as some might make us believe. None of them pays me! It’s a bit juvenile and straightforward.

It’s an inaccurate assertion. Open Source Development is an absolute threat to FLASH However, Adobe includes beyond Flash. This is one of the things that amazes me. People who fight with their teeth and claws against Adobe don’t realize that they can benefit from it. Dreamweaver CS5 already features “smart paste,” which allows you to add a bit that is Flash into a website directly…yes, as an HTML5 canvas. Some say the possibility of this, and I would recommend you try it out. Adobe has seen the potential of HTML5 easily, so why should it be a huge battle?

I’m not going to deny that Adobe produces great software for creativity that is among the top in the market and could lead the way by releasing excellent developing tools that work with HTML5. Adobe enthusiasts love to point at the reality that HTML5 has no dev tools at the moment, which is an honest (if somewhat hurried) statement.

I’m constantly hearing this in different forms, some of which are hilarious, like the time a young Adobe user said to me, “developing a web app in a mark-up language would be too hard” I say, no, my friend, it won’t be difficult, it’d be a complete nightmare! Canvas, for instance, the tag defines the boundaries of the element. All that takes place inside is controlled through JavaScript API. JavaScript API.

Some people consider this a terrifying possibility, and I’m not sure why, as JavaScript isn’t a complex language. It is important to remember that ActionScript is an adaptation of JavaScript; therefore, how simple could it be to develop a Flash-like development environment that uses the Canvas API? Easy enough, as I mentioned in my previous post, Adobe is already proving to be slowly moving in this direction. If they don’t, the next person will. It’s only with HTML5 since it’s open-source, there will be a lot of companies pushing the technology ahead, and we’ll see amazingly efficient and cost-effective tools that were never thought of from the inside of the Flash web.