4 ms·
Nice analysis, but only half of the story. As pointed out in the comments, you can make thick or thin clients in both native and HTML5. The issue is rather the
by ripperdoc 14y ago
Nice analysis, but only half of the story. As pointed out in the comments, you can make thick or thin clients in both native and HTML5. The issue is rather the one about lowest common denominator. HTML5 aims at working in very varied "runtime environment", where standards are bendable, bugs are rife and feature support a few years behind what native could muster. HTML5 is more difficult, and does not have all the tools, of the native environment. So the question is rather - will HTML5 develop faster than native and thereby be on par with it, or will it always be the straggler?
- chii 14y agoThere is incentive from the platform creators to make their native UI better and better, but not the same incentives for making the HTML5 support (if they are in charge of it, e.g., a browser). By this argument, native will always have features that HTML5 is not able to achieve.