|
2011-10-02
, 12:29
|
|
Posts: 1,625 |
Thanked: 998 times |
Joined on Aug 2010
|
#52
|
|
2011-10-02
, 12:40
|
|
Posts: 738 |
Thanked: 983 times |
Joined on Apr 2010
@ London
|
#53
|
|
2011-10-02
, 18:47
|
Posts: 303 |
Thanked: 146 times |
Joined on Aug 2009
|
#55
|
You mix apples with oranges and finish it off by countering your own argument.
Here you argue for native code, C or C++, together with SDL, GTK or Qt, which I'm guessing is there as something "platform independent".
But, that's exactly what HTML5 is planned to bring to the table. With a rendering engine for HTML5 available, it replaces GTK and Qt and supplies bindings for playing sound and video using yet another batch of native code. Just as SDL, GTK and Qt does.
This is just a red herring. Have you done any HTML(5)/JavaScript development? If you failed at it, does it make HTML5 a failure?
What has "usefulness" to do with energy consumption? Keep your fruits separated.
|
2011-10-03
, 06:49
|
Posts: 726 |
Thanked: 345 times |
Joined on Apr 2010
@ Sweden
|
#56
|
1. HTML5 is not, right now, available on the machines the previously mentioned libraries are available. And it will never be, especially on the older machines.
2. HTML5 is obviously not as fast as native library, because there is lots of parsing and scripting involved, which is slow and inefficient.
<html> <body> <h2>Hello World!</h2> </body> </html>
I didn't, but how is that relevant?
WTF kind of question is that? How can something be useful if it eats your phone battery significantly faster than what we had before?
|
2011-10-03
, 08:39
|
Posts: 303 |
Thanked: 146 times |
Joined on Aug 2009
|
#57
|
Was GTK or Qt available for all those platforms from the start? Of course not. It's a gradual process of porting, as always.
You mean, as with all and every browser out there parsing ordinary HTML and rendering text and images while running JavaScript?
On the relative scale, rendering engines are slower than "native code", nothing to argue about there, but they offer lots of nifty features that you need to know pretty well to use effectively in C/C++ to get the same feature set. This is part of the power of HTML(5).
Code:<html> <body> <h2>Hello World!</h2> </body> </html>
I dare you to write this simple program in C/C++ and get the same features and then claim that it's so much harder in HTML5. I double dare you to explain how the tools used for C/C++ are easier to use than an ordinary text editor and the "Reload" button in a browser.
It's relevant because your argument is incredibly weak. Just because you think HTML5 is harder to use than C/C++, it doesn't make it so. Especially since you didn't even try it (and I'm interpreting your answer kindly now excluding the "failing at it" option)
Something being useful isn't limited by battery consumption. I can run lynx (or even wget) in an xterm on my N900 and "surf the interwebs" but it's easier to do it using microB, a browser, even though it will "eat my phone battery significantly faster".
And for the record: I loathe having to write HTML and I wretch at having to write (and debug) JavaScript. I, like you, prefer C for most things.
I'm not defending the HTML(5) technology as such, I'm addressing your arguments.
|
2011-10-03
, 09:29
|
|
Posts: 738 |
Thanked: 983 times |
Joined on Apr 2010
@ London
|
#58
|
My arguments still stand. No HTML5 code will ever be near as efficient as native C code.
|
2011-10-03
, 21:24
|
Posts: 726 |
Thanked: 345 times |
Joined on Apr 2010
@ Sweden
|
#59
|
WTF... we have at least 3 libraries that have ports on pretty much all the OSes, and can be ported on any device that runs those OSes. And now you want developers to develop on yet a new thing, that is SLOWER, not widely adopted, and has little or no benefit over the existing things?
I am not sure what are you trying to say here. That whole HTML code can be replaced with one line of C code, if you already have a function to draw text at specific locations on screen.
Well, I triple dare you to write a HTML5 program that is even half as efficient (in terms of CPU cycles) than the equivalent C program. Did you see that fractal HTML5 demo? It is probably about 100K times slower than native code.
I never said HTML5 is harder to use than C/C++..
Totally irrelevant example, or 'red herring' as you like to say.
If you write an application in HTML5 or GTK, for example, the user should not see any difference.
it is about lazy application developers who don't want to make an extra effort to assure more efficient code.
My arguments still stand. No HTML5 code will ever be near as efficient as native C code.
|
2011-10-03
, 22:07
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#60
|
The Following User Says Thank You to mikecomputing For This Useful Post: | ||
Tags |
goodbye nokia, html != c/c++, meego is dead |
|
But, that's exactly what HTML5 is planned to bring to the table. With a rendering engine for HTML5 available, it replaces GTK and Qt and supplies bindings for playing sound and video using yet another batch of native code. Just as SDL, GTK and Qt does.
Have a look at the available HTML/JavaScript development tools out there. FireBug, for example, makes it easy to test and debug your code inside the browser that is then going to run the code which is something you can't just whip together if you're compiling and debugging your C/C++ code. Especially not when developing for a mobile device...
Since HTML5 a new, soon to be, standard, it's obvious that there are fewer developers that know it compared to some other established technology.