Search |
||
Speculations regarding Google Chrome OSPosted by joconner on July 9, 2009 at 1:57 AM PDT
Today's announcement of Google's Chrome OS is exciting in a few ways. I think it has implications for Java developers. With hindsight, I now think that Larry Ellison was hinting about Google's Chrome OS when he expressed some of his desires for JavaFX on small netbook-like devices. So, without any real knowledge and armed with nothing more than a vivid imagination, I provide some of my predictions/speculations for the upcoming Google Chrome OS and the devices it will power:
Ok, some of that's just silly, crazy talk...or is it? We'll see over the next few months. Oh, one last thing. I just cannot resist the urge to compare Google Chrome OS to Sun's Java OS. Do you remember that? I could hardly find any references to it, although I did find an old article called Inside the IBM JavaOS Project. At some point, Sun apparently enslisted IBM to help. At any rate, the Java OS project started (and ended) a long, long time ago. It's been a decade at least. Remember the Hot Java browser? I actually ran it and used it. I remember that one of our tests at Sun was to run the SwingSet demo on it. But now I'm just distracted. What was I saying? Oh yes, there are even more similarities. Java OS is to Google Chrome OS as the Hot Java browser is to the Chrome browser. Maybe Google Chrome OS will finally be the successful reincarnation of JavaOS? It's all fun to think about, and as I suggested, pure speculation at this point. »
Related Topics >>
Business Comments
Comments are listed in date ascending order (oldest first)
Submitted by fabriziogiudici on Thu, 2009-07-09 03:50.
Probably a better comparison would be with OpenMoko.
Submitted by opinali on Thu, 2009-07-09 05:28.
According to some reports, e.g from Ars, you are off the mark with some items: Chrome OS will not be based on Android, will not have a Java SDK - unless they add this as a bridge to run Android apps but that would be certainly secondary, and probably optional. Its browser will be Google Chrome with the V8 JavaScript VM (Android uses SquirrelFish); and the brower will be the primary SDK - augmented by Google's RIA tech like Google Gears and O3D. In this sense, the best comparision is with Palm's new webOS.
Of course I'd expect Google to reuse many low-level components from Android, like their customized Linux kernel, network stack, core media support, and other components that would be needed in a netbook.
Chrome OS will be powerful enough to run the full Java SE, so we can forget the major distraction that Android was. ;-)
Submitted by fabriziogiudici on Thu, 2009-07-09 05:36.
"Chrome OS will be powerful enough to run the full Java SE"
... it depends on whether Google will allow us to run it.
Submitted by opinali on Thu, 2009-07-09 07:28.
If the Chrome OS's browser is basically identical to the Chrome we know, i.e. a full featured browser including the interfaces necessary for plugins, then there's litte Google can do technically to stop somebody else to provide a JRE. Even in Android it should be relatively easy to port Java, remarkably after they introduced the native SDK.
And considering that Chrome OS will be a browser-centric OS, I doubt very much that Google would remove the plugin capacity to exclude not only Java but other important plugins like Flash, Acrobat Reader, custom security plugins used by online banks, etc. Smartphones can get away with this because the devices are not powerful enough, have no decent displays or keyboards, for a first-class unrestricted browsing experience; and users don't expect full PC-level functionality from these devices.
Submitted by mikeazzi on Thu, 2009-07-09 10:59.
The one thing I like about the Chrome OS/Browser is that they are taking the isolation concept to a new level within the browser with the use of separate address space for each tab. I wonder when Sun will wake up and smell the coffee and add Isolates support to the JVM.
Submitted by fabriziogiudici on Fri, 2009-07-10 10:46.
"Google can do technically to stop somebody else to provide a JRE"
Technically. In the perspective of "moral suasion", I'm sure Google can do a lot (surely a lot on Sun in the current situation, maybe after the Oracle buy things will be different). This would not be a problem for Java, as it's FLOSS and everybody could do the port. It could be a problem for JavaFX. I think there are no technical reasons for not having JavaFX on Android, but...
Submitted by fabriziogiudici on Fri, 2009-07-10 10:48.
"add Isolates support to the JVM."
Do you know that there is a complete specification for that? It's JSR 121 and it's three years old. Nothing has been done after the specification.
Submitted by coxcu on Fri, 2009-07-10 16:37.
I have lobbied (well, the occasional annoying email and random blog or forum post) Sun in the past to release the sources for both JavaOS and HotJava. Much of that was driven wanting to see what they could do for the Java Isolate problem space.
http://books.google.com/books?id=w7BQAAAAMAAJ&q=javaos&dq=javaos&ei=tMxX...
Submitted by comrad on Mon, 2009-07-13 03:06.
If it should be a WebOS it should also have support for Flash 10+, Silverlight, Java, JavaFX, Adobe AIR and stuff. A self called web-OS without those technologies might be difficult to be sold to Joe Customer.
Re
Submitted by eoinmorgan on Sat, 2009-10-10 04:08.
Re
Submitted by eoinmorgan on Sat, 2009-10-10 04:09.
Re
Submitted by eoinmorgan on Sat, 2009-10-10 04:13.
|
||
|
|