Skip to main content

How To Respond to Google Chrome OS

UPDATE: Fixed 'Response' to 'Respond' in title. Sorry about that.

We all have to do it, so I might as well take my turn.

First impression: no surprise here.

There are expectations in two forms here. We can expect certain things to come of this and we can expect certain things to disappoint us about this. There is a third, external expectation that techies will divide into a camp of people who think its Rilly, Rilly Important and a camp who thinks you're all wasting your time. I mean, gosh, its almost like this is exactly like any other topic we split down some arbitrary middle about. Get over it.

I Expect To Like:
  • Cheaper netbooks
  • Installing Chrome OS on old hardware
I Expect To Dislike:
  • Feeling like I have an OS that won't let me install anything but a browser
  • Not being able to install Android Apps
  • Not being able to run real Chrome on Android
  • Having no way to persist the state of a Javascript VM, so that I can close applications or save memory on long running ones and resume my work later
  • Still not being able to sync my bookmarks and open tabs and page states properly (or at all) so that applications that are just websites can easily move from my little netbook to my desktop
  • Not getting Android on netbooks, because Chrome OS gets pushed, instead
I Expect To Be Let Down About:
  • Getting Chrome OS on Tegra hardware with O3D
  • Google doing a funny video in time square asking What is an operating system?
  • Never having Google Notebook on a Google Netbook
My lack of pros in these lists that have anything to do with Chrome OS itself are not lost on me. I'm actually excited about it. I think its a really good thing. The availability of this certainly quality project will do great things for our perception of the web, the price points of netbooks, and Christmas in a down economy. The thing is, Chrome OS, at least initially, will be great for what it is not, rather than what it is.

Comments

Pereira said…
Hey dude,

As Eric just said there are a lot of commonalities between Chrome and Google’s mobile operating system, Android. “Although it appears they are two separate projects, there’s a great deal of commonality,” Mr. Schmidt said. “Eventually they may merge even closer.” ;)

The smarter choice for sure won't be to keep two different kernels/browsers and etc... ;)

Cheers.
Since everyone keeps thinking that Android will never get the Google Chrome browser.

http://www.readwriteweb.com/archives/confirmed_chrome_is_coming_to_android.php

^Here's a link to prove everyone wrong.
Calvin Spealman said…
I never thought we wouldn't see Chrome on Android, just that the timelines are strange for it not to have been the first move. They wasted a lot of resources getting the Android Browser built just to throw it away.
Pereira said…
Android Browser is pratically WebKit (Safari/KHTML). So Chrome without V8 Javascript and process manager :P. As we will have Chrome for Linux in a couple of months (maybe less), we will have for Android too. :)

Popular posts from this blog

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad.

Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems.

There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day.

The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad.

You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You unstuck …

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…