Their working with MS amounted to, what - adding a $2 MD card reader to the XO? I think that's all that it changed in terms of the hardware plan, anyway.
I have an XO. The card reader is bloody useful, if you ask me.
even iCab -a browser developed by one person- beat them to full compliance by months
That's disingenuous. The version of iCab (4.6) that passed the Acid3 test uses the same WebKit rendering engine as Safari and Chrome. And it beat Safari 4 to market by 1 day.
Not so much. You probably don't find Qt to be too inefficient, but Arthur does double buffering by default too. And for good reason.
Personally, I blame GTK2's obsession with double buffering everything.
Clearly, the Mozilla developers just forgot to call 'gtk_widget_set_double_buffered(false);'. That's what's been gumming up the works. Much appreciated, and thanks for your informed opinion on the matter!
My laptop: Fry
Wife's: Leela
Wife's old laptop: Amy
Printer: Zoidberg (dispenses ink)
Router: Bender ("bends" packets)
OLPC XO Laptop: Kiff (both small and green)
Car: Planet Express Ship (with which the 2006 Honda Civic shares a striking resemblance)
Cat: Zapp (cavalier, not too bright, doesn't wear pants).
I've been told by wifie that future pet names will include "Nibbler" and "Scruffy".
They updated the version of WebKit that they're using to one that passes the ACID3 test. That's something.
Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?
