How do you cloud?

“Cloud Computing” is one of those buzzword terms that’s been driving everybody nuts for a while now, at least from what I’ve seen. But what does it really mean to people? Often when a term gets thrown around enough to become a “buzzword”, it starts losing its meaning because people grow numb to it. Once that happens, you get pushback from people, even people to whom the buzzword applies.

Computing in “the Cloud” is one of those terms. Like the term or not, Cloud Computing is here, and has been here for a while now, and if you’re like most people on the Internet, it applies to you in at least some way, whether you admit it or not.

Here’s how it applies to you, and how it applies to me.

Continue reading

Midori 0.2.6: Simple, lightweight, but still needs work

In my ongoing search for something with which to tinker, I’ve occasionally run across the Midori browser, a fully GTK+2 integrated, WebKit-based browser with a focus on being lightweight and simple.

It had been a while since I gave Midori a try, so I thought that since they had released a few updated versions since my last look, I’d install it and give it a new look, because it seemed to have some promise the last time.

I did most of my testing on my 64-bit Mint 9 laptop, and I installed Midori 0.2.6, which was the version in the repositories. I used it for a week as my primary browser, only resorting to Firefox when I had to do something that I couldn’t get to work in Midori, which is my usual approach to evaluating browsers.

Continue reading

Clementine 0.4: Amarok 1.4 reborn!

I’ve lamented since last year that KDE’s radical change in direction left me — and a lot of others — going on an app-hunt. I’m really not a fan of the new Amarok, and I’ve been as yet unsuccessful in finding something to replace my beloved Amarok 1.4, even resorting to procedures like this one to install the old version.

Such procedures make a good stopgap for the time being, but sooner or later, that old thing will simply not work anymore. Once a program falls out of development, the clock is ticking on it remaining useful, and at that point, you have to face reality and find something with which to replace it.

Fortunately, I’m not the only Amarok 1.4 lover out there. It’s been forked, and the new version is called Clementine.

Continue reading

Opera 10.60 for Linux: A rant

I’ve made no secret of the fact that despite my open source advocacy, I’m still a longtime user of the Opera browser.

However, the past year has been pretty rocky in that respect; Opera 10.10 for Linux was plagued with a lot of bugs, crashes, and performance issues, rendering it practically unusable, even for an Opera fan such as myself, and despite 10.50 being released for other platforms in March, the Linux world was stuck with the problematic 10.10 (and eventually 10.11) release until this week.

Finally, after such a long wait, Opera 10.60 was finally released for all platforms on July 1st, so I was finally able to ditch Firefox and Chrome and go back to my browser of choice.

Or was I?

Continue reading

Thoughts on Google Chrome (stable) for Linux

As many of you are already aware, Google Chrome stable was released for the Linux platform on May 25th.

Google Chrome has been one of the fastest growing browsers, and a stable release for Linux has been a long time coming. I’ve played around with beta releases and found them so unstable as to be unusable as recently as just a few months ago, so needless to say, I was pretty interested in seeing what a release for Linux marked “stable” was like.

I’ve been using it as my primary browser since May 25th, so I decided I’d do a brief writeup of what I think of the experience so far.

Continue reading

One year and still going

In May of 2009 after hemming and hawing about it for far too long, I finally just bit the bullet and created this blog and registered I thought at the time that it would be a good way for me to keep track of some of my Linux and technology experiments, a place for me to go when I think “okay, when I was messing around with $whatever, how the heck did I configure that?”.

I also thought it’d be a good way for me to share geeky techie information with some of my close geek friends, particularly the ones who are always tinkering around like I am.

Today marks a year since I made that “Hello World” post, and now The Linux Critic is averaging over 18,000 unique views per month, and I’m still finding a lot of enjoyment in creating content here, even if it’s just the occasional unproductive rant about something that’s bothering me in the Linux world.

Even though I haven’t always been as regular with posts as I probably should have been, a fair number of you have continued to keep an eye on what I and my contributors (Joe and Patrick) have to say whenever we do manage to post a new article, howto, review, or whatever.

For that, and for the wonderful comments many of you continue to post — the ones of encouragement and yes, even the ones of disagreement — I say “thanks!”, because it’s very validating.

Linux is a tinkerer’s dream, and we love it. I know you do, otherwise you wouldn’t be bothering to read this or anything else here!

But going back to my original stated purpose with this blog, Linux can be better, and only by continuing to tinker, continuing to find those weak points, and continuing to point them out can Linux get better.

When I started this, I honestly didn’t think anybody (other than my friends and myself) would bother to read anything here. I said it was very validating to have so many regular readers and so many commenters, and this is why. It makes me feel like there is a wider purpose to this, that all this tinkering and tweaking and evaluating and technology exploration and subsequent discussion can lead to something good. It makes me feel like I’m still on the right track, and that makes it all worth it.

So, a year into this, I say again thanks for reading, following, commenting, and paying attention. It’s appreciated!

But I’m not done here yet. I have a lot more to talk about, a lot more Linux to explore, and a lot more to discuss, so stick around and keep reading!

— Trent