Posts Tagged: CSS


29
Jul 10

Thesis Wars

I’m about a week behind commenting on the story that pitted WordPress founder Matt Mullenweg against Thesis theme creator Chris Pearson, but I found myself pondering my allegiances again.  Essentially, the fight boiled down to this: Mullenweg was angry at Pearson for selling a theme that used PHP, WordPress code, and WordPress plugin API, all of which are licensed under the General Public License (GPL), without in turn licensing his own Thesis theme in the same way.  This license requires that projects utilizing other GPL-licensed code must be instilled with the same share-alike privileges for users, which means that Pearson was likely breaking an as of yet formally untested law by attempting to make all elements of his theme proprietary, and thus, limiting the rights of users to utilize what should have been freely available bits of code.

As the Mashable story to which I linked outlines, Mullenweg eventually came out on top and got Pearson to utilize a split license in which the aforementioned elements of Thesis are now GPL-licensed while the CSS and JavaScript present within the theme remains proprietary.

Thesis is a fantastic WordPress theme, and I’ve worked with it on a couple of different blogs.  If there were a WordPress theme for which I’d be willing to pay, Thesis would likely be the only one, and even though I’m generally a fan of free, open-source products, I can’t say I blame Pearson for charging for it even though so many theme developers have chosen to request donations instead of fixing prices.  I certainly side with Mullenweg when it comes to the licensing issue, but the CSS and JavaScript are what make Thesis a robust, highly customizable theme, so despite getting bits of it under the GPL, most of the real power of Thesis is still locked away behind the pay wall.

Ultimately, I think this is unfortunate.  Most of the ramblings I produce I attempt to place under one of the Creative Commons licenses, and I’m ecstatic to see CC provisions being used so frequently online these days.  Maybe I’m more comfortable with these licenses because I’d feel pretty damned guilty for being a prick about someone copping my rubbish for free, though I do usually request attribution.  I can’t say I’d feel the same way if I had put a great deal of time into developing a useful plugin, powerful theme, or program of some sort (not that I could).  I still think I’d simply request donations and continue on my way as I do try to donate when I’ve found a plugin especially useful.

It’s probably better to view the situation with equal parts ideology and practicality.  Open source and alternative licensing have democratized content production on the internet, but it may be overzealous to think the free model will work as an absolute.

RELATED READING: I’m sure many of you have heard of Lawrence Lessig.  He wrote a fantastic book called Remix that deals with rethinking copyright issues on the web.  You can download the book as a PDF for free.  Many of Lessig’s books are listed under Creative Commons licenses.

Share this with other foolish humans:
  • Facebook
  • Twitter
  • Google Buzz
  • Reddit
  • Digg
  • del.icio.us
  • Google Bookmarks
  • Tumblr
  • Posterous
  • Technorati
  • StumbleUpon
  • Yahoo! Buzz
  • Slashdot
  • email

12
Mar 10

Internet Explorer 6: A Rotting Corpse of a Browser

IE6 Must Die

Attirbution: http://www.flickr.com/photos/rohdesign/ / CC BY-NC-ND 2.0

Get off of it.  Don’t ask questions; just do it.

By now, it should be obvious to anyone with even a passing knowledge of better and more stable alternatives that Internet Explorer 6 is a husk of a web browser.  It is no more.  It has ceased to be.  Bereft of life, it rests in peace… You get the idea.

It used to be that IE6 was little more than a nuisance.  Sure, Firefox was better, and so were Safari and Opera, and it was a veritable pain in the ass to have to write conditional CSS simply to cater to those folks clinging to a browser released with Windows XP in 2001, but while these nuisances existed, for a long time, they were not so egregious as they are now.  In my worthless opinion, the browser battle really comes down to a face-off between Firefox and Chrome.  IE8 and Opera can’t hold a candle to them, and while Safari has undergone some nice improvements, I don’t think it’s in the same league.

That’s not what I’m on about here, though.  The rise of HTML5 is going to bring with it a number of innovations that will require the operational power of the newer and more robust browsers, and the reluctance to shut down a historical relic will hinder this progress.  IE6 also contains a number of security vulnerabilities that continue to compound as the browser grows obsolete.  Luckily, large websites and even some governments (Germany) are finally dropping IE6 support, and Mashable has dedicated a tag to its demise: IE6 Must Die.  Even Microsoft has finally called for users to upgrade.

Click around and read some of the articles on Mashable.  You’ll see why we need to leave this thing behind in order to move forward.

While there has been some debate as to how effective this tactic is, anyone who runs their own blog or website can contribute in some small way by installing one of a number of plugins/apps that alert visitors still on IE6 to upgrade their browser.  Naturally, change is going to be spurred more rapidly by large sites with heavy traffic dropping support, but you know what they say about drops in a bucket.  Every one of them counts.

As of February 2010, IE6 still maintained around a 20% market share.

Share this with other foolish humans:
  • Facebook
  • Twitter
  • Google Buzz
  • Reddit
  • Digg
  • del.icio.us
  • Google Bookmarks
  • Tumblr
  • Posterous
  • Technorati
  • StumbleUpon
  • Yahoo! Buzz
  • Slashdot
  • email