Last year Google showcased how Google’s Chrome OS moves all apps and data into a web browser, rather than running any Native apps.
As we know, Chrome OS is essentially Google’s Chrome web browser running atop a Goobuntu flavor of Linux (Ubuntu). It will not run local applications other than the browser itself. All other apps will be accessed inside the browser. Of course having a browser optimized from kernel level will give out exceptional performance.
Read more: Chrome OS Factsheet, Why its Relevant and Irrelevant
Now as per the latest update form one the Google employees, Chrome OS will provide remote access to “legacy PC applications” through a mystery process the company calls Chromoting.
In a message posted to Chrome OS Google groups, He wrote “We’re adding new capabilities all the time, With this functionality (unofficially named ‘chromoting’), Chrome OS will not only be [a] great platform for running modern web apps, but will also enable you to access legacy PC applications right within the browser.”
Gary, the author, calls this an “official” statement.
Neither Google nor Gary has responded to requests for comment. He’s been at Google since 2006, before which he was with Microsoft.
Chromoting would be “something like” Remote Desktop Connection, the Microsoft Windows service that gives you real-time access to distant PCs. Presumably, this means that Chrome OS will let you access applications running on your existing Windows, Linux, or Mac desktop.
The OS is not due for official release until the end of the year, when it will debut on netbooks.
Chromium OS source code includes references to a “chromoting plug-in,” and Gary mentions chromoting code during recent Chromimum IRC discussions.
Some other clients like Logmein.com, etc do something similar in the browser. Presumably, Google will include this sort of mini-client with Chrome OS as a plug-in, and you’ll then download a larger client on your existing desktop PC in order to access its Remote desktop & applications.
With Chrome OS, Google is intending on keeping everything inside the browser. Apart from what Google says, its a financial interest in moving more activity and more data onto the net: more web activity means more web ads, which mean more revenue.
Recently, we saw Remote printing from Chrome OS by routing jobs through its servers and back down to normal desktop PCs that, unlike Chrome OS, run print drivers.
Apart from Chromoting, Google had bee testing NaCl (Native code execution) by dynamically compiling javascript, html, css into native code and pump up execution. This could boost web applications to perform as good as desktop applicaitons.
The Native Client called NaCl is an open source initiative that targets on running x86 native code in web apps. Now Google has taken a step further by integrating NaCl into Chrome. Google has blessed the browser space with a unique feature that could pave future of Chrome OS, by running applications on the net.
Google intends to align web apps closer to native apps on a typical x86 operating system – Sincerely, I see this as the first step to Chrome OS.
> More at Google Chrome gets Native Code Execution with Native Client
Some might call this progress. Others might call it a workaround, we’ll have to wait a little longer before we can conclude.
We write latest in Google, Android, iPhone and Tech news, Grab them all via @taranfx on Twitter or subscribe below:
loading...
loading...