Apologies about the Slackware Review

A couple days ago, I reviewed Slackware 13.1. I wanted to see if I could use it post-installation, though from what I had read from commenters and writers on various blogs, it would be tough. At the end, it did prove to be as tough (and for me, fruitless) as I thought it would be. Though I did get to resolve a network connection issue, there wasn't really a whole lot interesting for me to see (other than a multitude of WMs in essentially vanilla form). Anyway, I wrote and published the review on this blog and it ended up in Linux Today and TuxMachines; owing to that, it got a lot of traffic and comments, most of which panned the lack of substance in the review.
It seems like most people who happened upon the review expected something substantive from a Slackware guru. Quite the opposite: I'm essentially a newbie who simply enjoys trying out different distributions from time to time. For letting down these readers (which is also a function of a lack of context, because though I make it clear on this blog that I am a newbie, that doesn't make it to Linux Today or TuxMachines), I am sorry.
Another mistake I made was expecting too much from Slackware. Usually, when I test distributions, I either expect a lot of things or nothing. For example, I would expect a lot of things out-of-the-box from a standard GNOME Ubuntu installation. I would not expect anything from Arch or Debian Standard. My mistake was associating Slackware included many WMs (especially KDE) out-of-the-box with many other niceties, like automatically configuring my network connection. I really should have included it in the group of distributions from which I expect nothing nice out-of-the-box. In addition, to make up for that, I probably should have read a good bit more about setting up Slackware post-installation. For these things, I am sorry.
However, there were quite a few comments that rhetorically asked why I chose to test Slackware if I knew that it wouldn't turn out so well. Well, the answer to that is that sometimes my expectations are defied (either way). In any case, I enjoy testing such expectations. In this case, my expectations (of a tough experience) were upheld. So please do tell me, is there anything wrong with that? It's either that, or I have seen the ugly side of the Linux community in the comments — the side that does not believe in helping out new users and only cares about those who already use Linux at the level of a trained professional. Maybe I've just been sheltered by the cordiality present in the Ubuntu and Linux Mint communities. Maybe it's just a matter of letting go of my innocence. But seriously, what's so horrible about having some expectations about Slackware, trying it out, and then writing about the experience?
In conclusion, I will say that this was probably a low point for this blog. Do not despair, as I have (better) reviews coming up in the coming days and weeks. I have learned my lesson with regard to Slackware, and you can be sure that I'll try not to make these mistakes again (especially if I get around to trying Arch).

How I Multiplied Subscribers and Page Views in 2 Weeks

Blogger Page View Statistics

I can't claim to speak for all bloggers when I say what I'm going to say. Whatever "advice" (if that's what it is) I give will probably be applicable only to bloggers who write about Linux/free culture/open source topics, as that's what I mostly write about (with the occasional diversion, like this post).
I would like to start this post (well, it isn't technically the very beginning anymore) by thanking Linux Today for posting some of my articles (mainly Linux distribution reviews); I would not have so many comments (which I hugely value and would love to see even more of) and subscribers if it wasn't for Linux Today accepting my submission of the KDE distribution comparison test. Since then, I've been able to get a couple more articles on Linux Today's home page, for which I am equally (if not more) grateful.
Well, there's one way to do it: submit your articles to Linux Today, as you will not regret it (and your article will most likely be accepted; furthermore, once you get your foot in the door and the article is positively received by the community, your future articles are more likely than the previous ones to get accepted).
I also want to thank TuxMachines for picking up on a couple of my review posts, as this has also hugely contributed to the traffic seen on this site; I didn't even send in the submission links, so I am hugely grateful for readers and editors of TuxMachines finding my reviews. In addition, I want to thank TechDirt for accepting my story on Microsoft's shutdown patent.
I have also created a Facebook page (and a "Like" widget for this site) and a Twitter account for this blog. If you are on these social networks, please do take a moment to either "Like" this site on Facebook or follow it on Twitter. While the Facebook page's notes application isn't working quite right (I'll try to fix it soon), I update the Twitter page with posts as they are published. That said, these are relatively new additions, so I don't think they really impacted the statistics.

Statcounter Page View Statistics

The Blogger statistics show that until August 29 or so, I was getting around 30 page views a day. It's not bad, but it could certainly be better. My comparison test was posted on September 1. That was when the page views went way up. I went from 35 page views on August 28-ish to 3500 page views on September 2. The Statcounter statistics tell a similar story: I went from about 27 page views on August 30 to 2700 page views on September 3, and now I'm averaging around 400 page views or so every day. I went from about 1000 page views total then to 10000 page views now, which is an increase of a full order of magnitude.
Subscribers are much harder to retain, as most people who visit blogs do not stay long to look around at other content besides what they've just looked out (which is why I am really thankful for the readers of this blog who do just that). That said, Feedburner's statistics on subscribers does show a tripling of my subscriber level; where before I was averaging 5 subscribers every day, now I'm averaging around 15 (and there was one day when I peaked at 39).
So, to recap: if you write about free software and related news and reviews, do not hesitate to submit posts to sites like Linux Today, TuxMachines, and TechDirt. Also, please do take the time (as I have) to list your blog on Technorati, BlogCatalog, and other blog catalog sites. These will all certainly contribute to higher traffic and more subscribers.
Dear readers, thank you all very, very much!

Review: Kubuntu 10.04 Trinity "Lucid Lynx" (Idea by Candid of Linux Today)

Main Screen: Ethais Wallpaper + Kicker

First off, I want to give a huge thanks and a shout-out to Linux Today reader Candid for suggesting that I take a look at Trinity. Your suggestion piqued my curiosity enough to make me want to do a full review and write-up. This one is for you. Thanks!
Reviewing this Linux distribution has reminded me of automotive news site Edmunds Inside Line's final review of the 2010 Mercury Grand Marquis in honor of Mercury's impending demise. It was a great nostalgic piece, as the car itself had turned into a weird mishmash of throwback controls and modern safety technology. For example, antilock brakes are present (as is traction control), yet the frame itself is a ladder-frame (like a truck, rather than a car's unibody frame) and the turn signals are operated by actual switches (as opposed to computerized systems). This is how I felt when testing Kubuntu 10.04 Trinity. It's a weird mishmash of old-school and new-school KDE.
So what is Trinity? For one, it's not the codename of this distribution — this version of Kubuntu 10.04 is still called "Lucid Lynx". Trinity is actually the name of a project that aims to revive, maintain, and further develop KDE 3.5 as a fork from the main KDE project. Yes, folks, KDE 3.5 has risen from the dead! [Insert dramatic sound effects here.] The project itself has had to overcome a lot of obstacles, chief among them the facts that Qt 3 has not been officially supported for 3 years (and rewriting the Qt code is just what the developers did for KDE 4) and that KDE 3.5 itself has not been actively developed or maintained for over 3 years. (Trinity is only a few months old.) That said, the Trinity packages are available for Ubuntu systems and can be installed alongside existing GNOME or KDE installations as a separate desktop environment. Trinity labels this newest release of KDE as KDE 3.5.11 (as the last official release was 3.5.10). Follow the jump to accompany me on a trip back to the future. (I had to say it. Sorry.)

Sometimes, Apple Doesn't "Just Work"

I was at a presentation this morning where the presenters were discussing research opportunities at MIT (called "UROPs" (Undergraduate Research Opportunity Programs)). The presenters showed a video about UROP that was put together last year to commemorate the 40th anniversary of the inception of UROP.
Before I continue, I would like to mention that at MIT, almost all of the school run computers (in the "Athena clusters") run Ubuntu 10.04.1 LTS, which is really cool. In fact, the Athena software is optimized to run on Ubuntu 10.04. Weirdly enough, I can't run the Athena software on my computer even though I run Linux Mint 9, which is basically Ubuntu 10.04 with some theme and included software changes. That said, I have exclusively seen Apple MacBooks used at presentations like these at MIT. This presentation was no exception.
The lady who started the presentation said a couple of things in general about UROP before showing the video. The video was on a separate DVD, and I saw her insert the DVD into the laptop. What happened next surprised me. There was no dialog upon insertion of the DVD asking what to do. She had to manually open the DVD's contents folder and search for the correct video. Even when that was done, she wasn't entirely sure which program to use (I suspect this is her first time using a Mac, considering that she struggled a little even to open the contents of the DVD); despite there being VLC Media Player on the laptop, she wasn't sure whether to open the video with iMovie, iDVD, DVD Player, or VLC. (She eventually picked DVD Player, and it worked.)
Macs are supposed to be easy to use and they are supposed to "just work". Then there's this. Your move, Apple.

I wanted to end this article by expressing by deepest thanks to the huge flood of visitors and commenters on this site. I never thought my article on KDE distributions would make it to Linux Today's front page; I feel extraordinarily lucky that it did. I also want to add that if you like any of the other content on this site, please sign up for updates through RSS or email; both options are pretty high up on the sidebar. I may even have an article exclusively for subscribers (at least initially) coming up, so that should be an incentive to sign up. If you haven't done so, please do it now! Finally, the next article (which, incidentally, is not that exclusive article I just talked about) should address the concerns of many of the commenters on the KDE comparison article. That should be a big hint as to what it is.