Yeh cool, but I have a sensation we are running in cercles.
Wouldn't it be easier to addopt nativeclient and use a mature, years tested code with http://code.google.com/p/nativeclient/ ?
Yeh I know, on the web you can "look" at the code, that's cool, but not always, how many time you did look at the gmail code for example, yeh it's preatty unreadable.because it's a compresed translated java code.
Nativeclient is very cool, and it allows you to run native code in your browser, but that does not mean native applications. You still have to port applications and any libraries to the nativeclient API/SDK (http://code.google.com/p/nativeclient-sdk/).
Nativeclient only currently exists in Chrome (and only if you run it using a special flag). Nativeclient itself is not yet mature. Javascript is everywhere, HTML5 will be everywhere soon. Nativeclient has a long road before it's widely supported in most browsers and on many architectures.
Comments
Yeh cool, but I have a sensation we are running in cercles. Wouldn't it be easier to addopt nativeclient and use a mature, years tested code with http://code.google.com/p/nativeclient/ ?
Yeh I know, on the web you can "look" at the code, that's cool, but not always, how many time you did look at the gmail code for example, yeh it's preatty unreadable.because it's a compresed translated java code.
Nativeclient is very cool, and it allows you to run native code in your browser, but that does not mean native applications. You still have to port applications and any libraries to the nativeclient API/SDK (http://code.google.com/p/nativeclient-sdk/).
Nativeclient only currently exists in Chrome (and only if you run it using a special flag). Nativeclient itself is not yet mature. Javascript is everywhere, HTML5 will be everywhere soon. Nativeclient has a long road before it's widely supported in most browsers and on many architectures.