3 ms·
A mix of HTML5 and Native will emerge. Check out 'Native Client (NaCl)' and 'Portable Native Client (PNaCl)'
by suyash 14y ago
A mix of HTML5 and Native will emerge. Check out 'Native Client (NaCl)' and 'Portable Native Client (PNaCl)'
- d1plo1d 14y agoWebGL strikes me as a much more likely and more open HTML5/Native hybridized future. I don't doubt there will be other hybrid technologies but I think WebGL is the first one that's here to stay. To clarify: I mean open as in open web here; that is to say that the WebGL GLSL code that gets compiled to run on the GPU is human readable when embedded in a website. AFAIK this is not the the case with NaCL or PNaCL. Moving back to adoption, NaCL has only currently been adoption by Chrome and Mozilla does not seem particularly interested in changing that. Related: * http://css.dzone.com/articles/mozilla-rejects-native-code http://css.dzone.com/articles/mozilla-rejects-native-code * http://news.ycombinator.com/item?id=4630057 http://news.ycombinator.com/item?id=4630057
- chc 14y agoI'm not so sure about that. I thought these technologies sounded very intriguing early on, but I don't think they're going to have much impact on the future. NaCl is weakly supported by Google, completely unsupported by other browsers and is totally architecture-dependent. It's quite possibly less portable than a normal native code app. PNaCl is basically abandonware as far as I can tell.