3 ms·
My problem with HTML5 is that you have to use JavaScript on the client. Until browser vendors implement other languages I'll stick with native.
by nuttendorfer 14y ago
My problem with HTML5 is that you have to use JavaScript on the client. Until browser vendors implement other languages I'll stick with native.
- hobonumber1 14y agoIf you dislike JS so much, why don't you use some cross-compiler?
- stream_fusion 14y agoIt's often difficult to gain mindshare with other developers and management.
- crististm 14y agoJS is (unfortunately) the only choice when you target browsers. I don't see any intrinsic advantage that can make it the go-to language. It's the lack of choice that I find problematic.
- randomdata 14y agoIs the problem Javascript or is it that the native environments provide nice and cozy frameworks that almost force you into strong development practices so there is a level of comfort that is generally not found in the browser? HTML5 is still the wild west, where anything goes. "jQuery spaghetti" is considered acceptable by many, and to convince developers who write in that style to provide structure to their application is asking them to do what often pushes them away from native development in the first place. Once you build up a solid MVC (or similar) framework in which to develop your Javascript/HTML5-based applications, the differences between native and HTML5-based development seem pretty trivial to me, and a few syntactical differences between the languages used on the varying platforms are no more than a talking point.