It’s been a little over a year since I reviewed the first Peppermint OS, and while I liked the first effort on this new project, I’ve been really looking forward to Peppermint Two. Well, my wait was over as of last week, so I was able to kick the tires and get a good feel for it after installing and using it for a few days.
And it didn’t disappoint!
Some of you who have been following this blog for a while may remember my post from 2009 where I was lamenting my lack of decent Linux-friendly MP3 player options out there to replace my aging Archos device.
Well, I still haven’t found one. However, thanks to Rockbox and a used device I bought from a friend, I have a stopgap that will hopefully last me until the portable music player electronics market sorts itself out.
Let’s face it. Browsers suck. In my ongoing search for a browser that meets all my needs, I’ve frequently found myself compromising in one way or another, and while I have good things to say about almost any browser, I can’t say that I “love” any of them.
So this is less of a list of “my favorite browsers”… I don’t have one of those. Instead, I present you with my list of The 5 Browsers That Annoy Me The Least.
A few weeks ago, I made a post here talking about what I’m doing lately in technology (cleverly labeled “What I’m doing lately in technology” ;)) and some of the comments on it really got me thinking about the approach that I have been taking on the specs for my next desktop computer will/should be. What am I going to use it for? Do I really NEED as much modularity as I’ve always insisted upon in the past? Should I be thinking “sleek, powerful, and small”, rather than “big, modular, and does everything”?
So I thought I’d sort some of this out here, by doing some thinking out loud, and hopefully getting some feedback from the rest of you.
Real life gets crazy sometimes, and blogging outside of the quick and sometimes poorly-thought-out rant takes time, so I haven’t been updating here anywhere near as often as I’d prefer.
So I thought I’d pound out a few quick paragraphs on what I have going on lately in terms of technology… what I’m running where and why.
With Oracle demonstrating yet again that they just don’t get it, and with The Document Foundation now truly forking OpenOffice.org into the new “LibreOffice“, we’re beginning to see where the lay of the land lies for the future of open source where documents, presentations and spreadsheets are concerned.
I think it’s a good idea for those of us in the open source community to make sure our voices are heard on this pivotal point in this project.
I got up this morning and saw this, which led me to a pretty serious WTF moment, all before having my morning coffee.
From the article:
Mozilla’s Director of Firefox, Mike Beltzner confirmed the fact that an x64 flavor of Firefox won’t be added to the existing x86 version, per the 32-bit/64-bit Internet Explorer 8 model.
Firefox users should not despair though. Fact is that Mozilla hasn’t given up on delivering a 64-bit version of Firefox, just not with Firefox 4.0.
This implies that maybe there will be a 64-bit release for Firefox 4.1? Maybe? 4.2? 5.0? Will there be one at all? Ever?
I think that they should probably be a little more open about when there will be, and why there’s a delay.
“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.
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.
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.