{"id":2189,"date":"2011-09-18T03:14:59","date_gmt":"2011-09-18T08:14:59","guid":{"rendered":"http:\/\/www.bytebot.net\/blog\/?p=2189"},"modified":"2011-09-18T03:15:04","modified_gmt":"2011-09-18T08:15:04","slug":"google-native-client-chrome-aboutflags","status":"publish","type":"post","link":"http:\/\/www.bytebot.net\/blog\/archives\/2011\/09\/18\/google-native-client-chrome-aboutflags","title":{"rendered":"Google Native Client & Chrome about:flags"},"content":{"rendered":"

I stumbled upon Google Native Client<\/a> today. It looks really interesting and you can see why Google seems to be targeting<\/a> their technologies for the Chrome browser first (link with regards to Dart<\/a>, their future<\/em> of JavaScript; quote: “We will strongly encourage Google developers start off targeting Chrome-only whenever possible as this gives us the best end user experience.” – Mark S. Miller).<\/p>\n

\"GoogleThe promise of better in-browser games for example, is what excites me about this initiative. There is also the promise of better native\/traditional desktop apps, running in the web browser. I was at a show recently where I saw this HRM app that is Windows-only and their proposal to run it on Linux? Use virtualization. This is something they might find useful, for example.<\/p>\n

Try out the example apps<\/a>. Its surprisingly easy to get started<\/a>. On OSX, you can see that when running the Pi example, the Native Client module is using quite a whole load of CPU time (in Chrome, do Window -> Task Manager).<\/p>\n

In all that, I learned about Google Chrome’s about:flags<\/tt>. You need to enable Native Client support and restart Chrome to get this all working. There’s a fairly good about:flags resource<\/a>; clearly lots more things to play with there (and helps me understand what the idea being the ChromeOS\/Chromebook is now).<\/p>\n

Share this:<\/h3>