Linked by snydeq on Tue 16th Aug 2011 16:46 UTC
Web 2.0 InfoWorld's Peter Wayner discusses the 11 hard truths Web developers must accept in making the most of HTML5 -- especially those who are looking to leverage HTML5 in hopes of unseating native apps. 'The truth is, despite its powerful capabilities, HTML5 isn't the solution for every problem. Its additional features are compelling and will help make Web apps formidable competitors for native apps, but security issues, limitations of local data storage, synchonization challenges, and politics should have us all scaling back our expectations for the spec.'
Thread beginning with comment 485500
To read all comments associated with this story, please click here.
crashed on point 1
by RaSaR on Wed 17th Aug 2011 11:42 UTC
RaSaR
Member since:
2009-03-30

Just let us look at security. When security *does* matter, it is the right way to have access to the sources. You *can* look for security issues. You can't do that on closed systems. You have do secure your system, regardless of the point. Regardless if the user can see the code or not. They can always disassemble or you have to do it server-side. It will be attacked sooner or later.

*But* there is another thing that is a part of this all: Copyright. Do you have a license for all the parts of the html5 & JavaScript code? And a redistribution license? And a license that doesn't need to be accepted by the user? (Just imagine: enter a url and get asked if you like to accept the printed GPL. And you have to accept it to get the JavaScript Code, which renters the web site, ... )

This might not be relevant now. But when lawyers start to sue site owners and users, it will be different. And as we know the lawyers, it will be.

Reply Score: 1