Linked by Thom Holwerda on Sat 5th Jan 2013 16:41 UTC
Thread beginning with comment 547447
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
I think general the techniques for achieving performance are pretty much the same. For example, on Windows 8 which uses HTML5/JS as an option for app development, a lot of the Windows-isms are built on existing HTML5 solutions. Async built ontop of JS promises, view state swapping on top of Media Queries, etc.
Yeah but there is a huge difference between writing a html5 app that will be served over http to a variety of web browsers versus a html5 app that is only run by the os' html renderer.
Honestly, I think we need a better framework than HTML5 that is designed from the ground up to run apps. Thus, you keep HTML5 for web pages and content, and a different framework for apps. Either that, or find a way to make scripting for HTML5 on the client side language agnostic, instead of all these janky wrappers for Javascript we have now.





Member since:
2005-11-29
The question of the viability of web applications is an important one in the context of OSNews given that a lot of mobile OSes are using HTML5 as their application platform.