In this post for the Disruptive Competition Project, I take exception to the “Google is doing this to stick it to Apple” interpretation of the company’s forking the WebKit code into another open-source browser engine, Blink. I think this is good for Chrome users and good for the Web at large—and that if Google wants to subvert Web interoperability and sandbag Apple, there are other things you should watch out for.
A more business-oriented take on SXSW for the Disruptive Competition Project blog, in which I discuss things that the conference did and did not clarify in a few tech frontiers: 3D printing, HTML5 apps, mobile finances and our own unpredictable human reactions to all of these changes. I threw in a gratuitous shot of a 3D printer extruding the SXSW logo because, really, why not?
This week’s USAToday.com column unpacks a long-running, just-solved problem with printing JetBlue boarding passes on a Mac—which, as far as I can tell, is due entirely to the airline enlisting the Flash plug-in to process the PDF in a browser window—and notes another instance of a company using Flash for the wrong task. It wraps up with a reminder about how to take screen captures in iOS (easy) and Android (it depends).
A USA Today reader asked that question, so I answered it. IE9’s cleaner UI, better standards compliance, upgraded security and improved Web-standards support all justify upgrading. The column goes on to suggest Google’s Chrome as a good alternative, then concludes by explaining how to use two new non-Google search engines as your default in Chrome.