sh wrote:
Wow, I had no clue about some of those points - Thanks Sholom!
T

On 2011-08-18 10:38:09 -0400, sh <shamada (AT) prupipe (DOT) com> said:

I agree with many of the comments on that article. The issues pointed
out are mostly related to any type of web-based application. Very
little of it was specific to HTML 5.

--
Kevin Powick

On 8/18/2011 3:38 PM, Kevin Powick wrote:
I also thought so.

I agree that this is not a particularly html5 list. This is quite a mixed list, including both concerns for developers (the usual suspects here with cross-browser compatibility, client-side security, and local storage) that are not html5-specific and concerns for companies adopting software, such asSaaS.

It is a worthwhile list if considering the pros and cons of writing web-based software compared to writing software that runs directly in the OS rather than software that runs in a browser run-time environment, but there are no big surprises nor much that is about html5, it seems.

The biggest downside of an odd list like this (pouring developer and end-user issues together) is that it might make someone think they should not develop software using an html5 doctype. Pretty much everyone writing a new web app today would be well-served by using an html5 doctype. You lose nothing by doing so, in spite of what one might think by reading the title of this.

--dawn