View Single Post
danramos's Avatar
Posts: 4,672 | Thanked: 5,455 times | Joined on Jul 2008 @ Springfield, MA, USA
#48
Originally Posted by Texrat View Post
When I heard the Tizen details at AppUp Elements, my first thought was that most apps would be hybrid HTML5 + device native code. Intel in fact confirmed that at our "fireside chat". So don't get too hung up on HTML5's shortcomings. There's an API for that.
Now, that sounds a lot like Chrome's NaCL. Hmmmmm

Originally Posted by Texrat View Post
Compatibility of course. Instead of recoding 100% of an app to run across multiple platforms, code an HTML5 layer for consistent look and feel for all and address unique aspects with lower-level code. So that the average app could be, say, 50% common code and 50% native. That saves time for companies like Rovio who like to land on every platform.

In addition, not every app needs the native horsepower or functionality. HTML5 will be able to address a great many handy little utilities by itself.

I can understand why C++ developers get overwrought about paradigm shifts like this one, but really, there is nothing to fear, belittle or berate. Just another tech evolution.
Yeah... who needs native code to run a calculator app, a hangman game or even a fart app? Think about it! INDEPENDENTLY CROSS PLATFORM FART APPS!

Now, for the 3D shooter or fighter, you might need native code at least involved, sure...

Originally Posted by jo21 View Post
no, because there is nothing like native code, C specially, and pretty much those engines likely written in C.
as far as performance there is nothing close as pure breath C.
But of course "there's nothing like it," except anything that IS ultimately like it. (You really didn't state anything.) Let's hear some genuine reasons, please, otherwise you have no basis for your refutation.

I, on the other hand, can point RIGHT UP AT THE TOP OF THIS POSTING to Texrat's posting about Intel's HTML5+native code position in Tizen and then to my reply to his post about NaCL (i.e. Here.. here's an article you should read). The benefit there is that you get the best of both worlds: apps that don't need it (probably MOST), don't NEED to be written in C and can benefit from HTML5's WIDE platform range--but if you're arsed enough that you need to, you can write native C code.. and then wrap it in HTML5 so that it can distribute to platforms that can run that native code.

FAR better than pure C native code. NO disadvantage.. unless you're Microsoft and this kills your PC platform strategies and profitable licenses.
__________________
Nokia's slogan shouldn't be the pedo-palmgrabbing image with the slogan, "Connecting People"... It should be one hand open pleadingly with another hand giving the middle finger and the more apt slogan, "Potential Unrealized." --DR