All my pet peeves against Linux rolled into one. From Google and Adobe engineers, no less. And of course, most of the replies are “yes but we’re free, we have choice, etc…”. *sigh*.
Archives
- May 2012 (1)
- October 2011 (1)
- August 2011 (1)
- June 2011 (1)
- April 2011 (1)
- February 2011 (1)
- August 2010 (2)
- June 2010 (1)
- May 2010 (2)
- April 2010 (2)
- March 2010 (1)
- February 2010 (1)
- January 2010 (2)
- October 2009 (1)
- September 2009 (1)
- June 2009 (1)
- May 2009 (1)
- April 2009 (1)
- March 2009 (1)
- February 2009 (1)
- January 2009 (3)
- October 2008 (1)
- September 2008 (2)
- August 2008 (3)
- June 2008 (4)
- April 2008 (3)
- January 2008 (1)
- December 2007 (3)
- November 2007 (1)
- October 2007 (2)
- September 2007 (1)
- August 2007 (3)
- July 2007 (3)
- June 2007 (1)
- May 2007 (2)
- April 2007 (4)
- March 2007 (5)
- February 2007 (4)
- January 2007 (7)
Blogroll
Mmm, I think that controversy was all a bit weak.
I mean, we all know that the conclusion is broadly true — the libraries and services available across Linux distributions make for a scruffy, frustrating and often unreliable target. That just doesn’t seem to me like the primary problem here.
I mean:
– it’s hard to port anything to or from Windows
– a modern web browser does a lot of stuff and is hard to port anywhere
– you have a few more decisions to make on Linux than on Windows (though really, not that many more — there are plenty of competing toolkits on Windows too)
– Chrome seems to do sandboxing at some level that I can’t pretend to understand anything about but that is apparently fiddly to do and needs kernel support
– Chrome developers have put a lot of work into making sure it feels shiny and nice and snappy etc to use on Windows, and much of that work doesn’t port at all
– you can’t please everyone
I’m not really seeing the part that explains whether, or why, it’s been any harder porting Chrome to Linux than porting it to OS/X, for example.
(Of course the one area where Linux really _is_ harder is in packaging and deployment, and they aren’t even talking about that yet! What joys we have yet to come.)
One thing I did find amusing about that Slashdot thread was seeing it descend once again into the argument about whether we were or weren’t sufficiently warned about the instability of KDE 4.0 when it first came out. I wonder when, or whether, that argument will ever stop?
Chris