In a series of articles (part I, part II) during the month of July, OfB's Timothy R. Butler explained why he felt that KDE needed to move beyond the Qt toolkit it uses as a foundation. In that series, he asserted that the licensing of Qt is becoming a stumbling block to the desktop's adoption. Eric Laffoon, the project lead for KDE's Kdewebdev module, takes exception to Butler's arguments and makes the case for his view on the issue of Qt, below.
EXCLUSIVE. Earlier reports circulating around the Internet concerning Apple's inclusion of a Trusted Platform Module (TPM) chip in Intel-based Macs were incorrect, OfB was informed. News of the inclusion of the chip, based on the technology formerly known as Palladium, had spread across the Internet as wildfire in recent days and many news outlets, including Open for Business, had published commentary on the dramatic revelation of the technology's inclusion.
Word came out earlier this week that Apple's Mac OS X on Intel developer kits depend on TCPA, still often known by its old name, Palladium. While Odysseus is long since dead, it is easy to see why Apple may be fearful of piracy as it moves to the x86 platform. The question is: exactly how does this impact the end user? That is not exactly clear just yet.
Over the last few weeks I have addressed licensing and usability issues with GNU/Linux desktops. One of the points raised against my arguments had to do with the need for companies providing Free Software to make money, namely, the need for Trolltech to make money. It is with the greatest irony that I now find myself discussing one of the new features in KDE 3.5 (although not exclusive to KDE) intended squarely at preventing some from receiving their dues.
Last week I promised to demonstrate why I am not a GNOME zealot simply looking to try to give KDE a hard time. In actuality, I don't use GNOME much at all, these days. Or KDE. I do keep up with them, but my actual desktop home is elsewhere. “Hey, Clippit! Stop staring at me.”
I knew when I mentioned something negative about the GNU Project's General Public License (GPL), in my column last week, I would inevitably be accused of arguing the GPL was a bad license. I knew this would happen despite my qualification to the argument that I had released code under the GPL myself. What did not fit into that piece shall now be dealt with: is the GPL a bad license?
It started out as a simple project: with the prospect that I'd be away from my desktop computer for a few weeks, I wanted to beef up my laptop's meager 256 megs of RAM. Having purchased my 12” PowerBook one release cycle before Apple boosted the RAM to the 512 megs it really should have had to begin with, it was long past time I embarked on opening up the case and upgrading. One thing was stopping me: I couldn't open it.
Thinking on the issue of licensing and KDE, an old hymn came to mind. “As it was in the beginning, is now, And ever shall be…” Yes, the issue of licensing has been a perennial problem for the Free/Open Source desktop and I would suggest its biggest licensing issue remains: the GPL.
This time last year, we inaugurated the Tim's Gadgets column by looking at Skyrocket Software's excellent Digital FireworX (review) screen saver and stand alone application. Digital FireworX was and is an impressive screensaver that displays the largest collection of simulated fireworks I have encountered anywhere. But, what if it could get even better?
Sure, it has been rumored for years. Sure, any technology observer even slightly familiar with Apple knew that Mac OS X had been run in house on Intel. But, Apple parting ways with the processor it has spent all of these years promoting? If Apple was a few millennia older, without doubt this would have been prophesied as a sign of the apocalypse. The real apocalypse may not be here yet, but the computing world has just seen one of the biggest earthshaking announcements in years. Now Apple faces one of the hardest projects ever put forward for a computer company in its position: keeping backward compatibility.