Oooohh.. Day two of Pixel porn.

So ChromeOS wasn't horrible, but running a native environment (currently still testing using a livecd just to see that it all works) really makes the screen come to its own. The ChromeOS browser decision to do scale things by double pixels is probably the right thing for introducing people to this screen, but it also holds you back from seeing just how nice the screen is.

Sure, with the true resolution exposed to the web browser, things are small. Just how I like it. You can have two browser windows open side-by-side, and they both look beautiful. The people who think that wide-screen displays are better because you can do that side-by-side thing don't seem to realize that you can do the same thing with full-sized screens, and just get more vertical space too.

Of course, I don't actually do two browser windows side-by-side, I read email in one browser and have a few terminal windows open, and often cut-and-paste between the two (with "git pull /paste-from-email/" being one of the more common things I do).

I think ChromeOS isn't necessarily a bad idea, but I think Google is being a bit too timid about it, and limiting things a bit too much. And that may make sense if your hardware is limited (ie slow Atom or ARM CPU, cheap 1366x768 panel), but on this machine it's really holding the hardware back.

Of course, if you really believe in touch-screens, you can't have those tiny graphical elements. With the kind of small detail I want, my fingers look like Godzilla-like sausages trampling all over Tokyo. No fine control.

So I kind of like the concept of touch-screens, but at the same time I don't really see how you can get the required precision.
Shared publiclyView activity