3 ms·
Yes, but it will be ready, and the question is will devs and firms that have invested all their time into native development be ready too? It would be prudent t
by marknutter 14y ago
Yes, but it will be ready, and the question is will devs and firms that have invested all their time into native development be ready too? It would be prudent to be ahead of the curve when the horizon is so clearly visible.
- mattmanser 14y agoIt was also clearly visible 3 years ago. It's nice to be an HTML5 advocate, but lets be realistic, it's 3-4 years before HTML5 will be coming even close to native in performance or tooling. In the meantime all those native developers will be kicking your ass in earnings and functionality.
- marknutter 14y ago> In the meantime all those native developers will be kicking your ass in earnings and functionality. There's no need to get testy. There's no reason why HTML5 proponents can't implement some or even all of their apps in Native code (as I do). Without getting into a religious war, though, it's important to understand where the puck is going in addition to where it is currently.
- spydum 14y agoThe problem with being a platform that serves such a large audience (indeed, one that gets paid based on the eyeballs it can sustain) is that you need to cater to the largest range of devices and their performance. It's the same reason enterprises still support such obscure browsers and OS's (XP/IE6). They just aren't willing to sacrifice the overall experience of those who are slow to upgrade in favor of pushing the technology forward.
- marknutter 14y agoYou don't have to support obscure markets if you don't want to. I'd say covering iOs 5+ and Android 2.3+ is going to cover an area most companies would be pretty happy with. And let's not forget that OS fragmentation affects Native developers just like it does HTML5 developers (especially on Android).