Linked by Thom Holwerda on Wed 18th Nov 2009 17:45 UTC
Google Okay, so it's not an actual release as Arrington predicted last week, but Google will indeed take the wraps off its Chrome OS tomorrow. The company will hold an event tomorrow at its company headquarters in Mountain View, California, where it will unveil its plans for the operating system. Update: An OSNews reader has uncovered possible evidence that Chrome OS uses X, Clutter, and Slim.
Thread beginning with comment 395313
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: X ??? WTF for!
by DOSguy on Wed 18th Nov 2009 22:37 UTC in reply to "X ??? WTF for!"
Member since:

I think you should read more on the subject of X and window managers.

"X provides the basic framework, or primitives, for building such GUI environments: drawing and moving windows on the screen and interacting with a mouse and/or keyboard. X does not mandate the user interface — individual client programs handle this."

Reply Parent Score: 2

RE[2]: X ??? WTF for!
by Tuishimi on Wed 18th Nov 2009 22:48 in reply to "RE: X ??? WTF for!"
Tuishimi Member since:

This is true, and I am glad you mentioned that. I felt myself getting both irritated and deflated thinking this would be JALD with some fancy front-end. But just because X is involved doesn't mean the UI is driven by it. It is a very extensive library of tools. In a way they would be crazy NOT to use it.

Reply Parent Score: 2

RE[2]: X ??? WTF for!
by krreagan on Wed 18th Nov 2009 23:28 in reply to "RE: X ??? WTF for!"
krreagan Member since:

I know what X is bloody for! I reiterate! It's a mistake to use X!


Reply Parent Score: 0

RE[3]: X ??? WTF for!
by cushioncritter on Thu 19th Nov 2009 06:39 in reply to "RE[2]: X ??? WTF for!"
cushioncritter Member since:

Perhaps you were thinking of something like directfb or SDL? Unfortunately, the various kernel framebuffer drivers are not in very good shape, and the maintainer of one very important one, intelfb, recently hid it in the kernel build options (to avoid further bug reports) so that it is only built, in his words "for specialty applications like embedded devices". The framebuffer driver that does work, vesafb (for example, with vga=791 in lilo/grub), is unaccelerated and one needs a fast CPU to watch video without frame dropping or the audio/video becoming unsynchronized. Examples of machines that would use the intelfb driver (if it worked) are Dell laptops, Sony laptops, and many desktop machines.

Reply Parent Score: 1