4 ms·
I'm not so sure Google's long term strategy is to bet it all on browser based clients and reach at the expense of user experience. They have NativeClient in Chr
by Detrus 15y ago
I'm not so sure Google's long term strategy is to bet it all on browser based clients and reach at the expense of user experience. They have NativeClient in ChromeOS, which may be a play to write a more traditional OS but better merged with the web.
The current state of the web is such a crappy experience for regular consumers that Apple's model could make some headway against it and Google wouldn't want to be moving at the pace of standards against them.
- glassx 15y agoAgreed. I think they're both fighting at both fronts, when you consider how Android embraced the app model and even expanded it (widgets etc), and how Apple was the most vocal of the HTML5 advocates...
- dodecaphonic 15y agoNativeClient is a cool technology, from a pure, geeky POV. Maybe awesome stuff will be done with it, to the point of steering other browsers in its direction, but right now it's a case of having a "Designed for Google Chrome" badge on you front page or developing two code bases, one with JavaScript, another with C++, just to have the same reach you would without it -- only to end up with a crappy user experience for a lot of people. The only way I see of furthering NaCl's agenda is if Adobe, Autodesk or some other company with a little cash to burn decides to write one of their apps (say, a Photoshop Express, or maybe a Sketchbook Pro) with it and prove in the market that there's a future in that approach. Otherwise, it will forever be just a cool hack.